Must Have Free System Administrator Tools

Here is my list of free must have system administrator tools for performing system tasks and troubleshooting. These tools can perform different functions, for example: checking your hard drive's S.M.A.R.T. counters to see if its healthy, backup your Windows registry, manage the system processes that are running, etc.

All of these tools can be stored and run from a USB flash drive. So that you can always have them with you when you need them most.

• Autoruns: Allows you to view and manage which programs are configured to startup automatically when your system boots and you login.
• Process Explorer: Allows you to view and manage system process. Here is a brief excerpt from the Sysinternals site, explaining what this program can do: "shows a list of the currently active processes, including the names of their owning accounts, ... you'll see the DLLs and memory-mapped files that the process has loaded."
• EURNT: Backs up the Windows Registry on your local computer.
• If you don't want to use EURNT, check out MSKB 322756: How to back up, edit, and restore the registry in Windows XP and Windows Server 2003
• Ethereal: Great for network diagnostics and troubleshooting.
• HDTune: View the S.M.A.R.T. information on your hard disk. S.M.A.R.T. is a technology that tracks the current condition of your drive (such as temperature, hours used, etc.).
• PsTools suite: Contains great tools like: PsExec, PsUptime, PsShutdown, PsLoggedOn, and more.

Published By

S.G.Godwin Dinesh.MCA

Sr.System Administrator

Is Offloaded Data Transfers (ODX) working?

Offloaded Data Transfers (ODX) is a new data transfer strategy that makes advancements in moving files.  Only storage devices that comply with the SPC4 and SBC3 specifications will work with this feature.  With this feature, copying files from one server to another is much quicker.  This feature is only available in Windows 8/2012 and above as both the source and the destination.
This is how it works at very high level:

• A user copies or moves a file by using Windows Explorer, a command line interface, or as part of a virtual machine migration.
• Windows Server 2012/2012R2 automatically translates this transfer request into an ODX (if supported by the storage array) and it receives a token that represents the data.
• The token is copied between the source server and destination server.
• The token is delivered to the storage array.
• The storage array internally performs the copy or move and provides status information to the user.

Below is a picture representation of what it looks like.  The top box is the way we are used to seeing it.  If you copy a file from one machine to another, the entire file is copied over the network.  In the bottom box, you see that the token is passed between the machines and the data is transferred on the storage.  This makes copying files tremendously faster, especially if these files are in the gigabytes.

For more information on Offloaded Data Transfers, please refer to

Windows Offloaded Data Transfers Overview

Many Windows installations have additional filter drivers loaded on the Storage stack.  This could be antivirus, backup agents, encryption agents, etc.  So you will need to determine if the installed filter drivers support ODX.  As a quick note, if the filter driver supports ODX, but the storage does not (or vice versa), then ODX will not be used.
We have filter manager supported features (SprtFtrs) which will tell if filter drivers support ODX.  We can use the FLTMC command, as shown below, to list filter drivers and their supported features.  For example:
X:\> fltmc instances
Filter      Volume Name    Altitude   Instance Name  Frame  SprtFtrs
----------  -------------  ---------  -------------  -----  --------
FileInfo    C:             45000      FileInfo       0      00000003
FileInfo    I:             45000      FileInfo       0      00000003
FileInfo    D:             45000      FileInfo       0      00000003 <-it and="" both="" offload="" read="" span="" supports="" write="">
FileInfo    K:             45000      FileInfo       0      00000003
FileInfo    \Device\Mup    45000      FileInfo       0      00000003
You can also see the Supported Features available for a filter driver in the registry:

HKLM\system\CurrentControlset\services\

The SupportedFeatures registry value contains an entry. If it is 3 as in the above FLTMC output, is supports ODX.
Now that we have determined that ODX is supported by the required components, is it actually working?  You can see the ODX commands FSCTL_OFFLOAD_WRITE and FSCTL_OFFLOAD_READ captured in a Process Monitor trace when it is working.  When ODX is working, we see the following in Process Monitor.

In case a target fails the Offload, it does not support ODX, or does not recognize the token, it can give a STATUS_INVALID_TOKEN and/or STATUS_INVALID_DEVICE_REQUEST as the result.

Other reasons why it might not work :
1)    Something above Storage stack such as encryption or File system driver (Encryption filter, etc.) can cause it to fail.
2)    Even though two disks/volumes might support offload they might be incompatible. This has to be established by involving the Storage Vendors.
It is not a recommendation, but for informational purposes, you can disable ODX functionality in the registry if so desired.  You can do this  with a PowerShell command:

Set-ItemProperty hklm:\system\currentcontrolset\control\filesystem -Name "FilterSupportedFeaturesMode" -Value 1

Or, you can edit the registry directly.  The value of 1 (false) means that it is disabled while the value of 0 (true) means it is enabled.  When this change is made, you will need to reboot the system for it to take effect.
One last thing to mention is that you should always keep current on hotfixes.  This is especially true if you are running Failover Clustering.  Below are the recommended hotfixes you should be running on Clusters, which include fixes for ODX.

Recommended hotfixes and updates for Windows Server 2012-based failover clusters
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters

Other references:
http://technet.microsoft.com/en-in/library/jj200627.aspx
http://msdn.microsoft.com/en-us/library/windows/hardware/dn265439(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/windows/desktop/hh848056(v=vs.85).aspx


Published By
S.G.Godwin Dinesh
Sr.System Administrator

NTLDR Missing

Press any Key to Restart:

Solution:

1. Change your pc boot Priority and make first boot CD- ROM/DVD
2.Than restart from CD and wait till it ask you for press r for Recovery
3. Press “R”
4. Choose which windows if you have more than one OS install in your pc write the number and press enter key
5. Provide your pc's administrator password and run below command to reslove the problem
copy e:\i386\ntldr c:\
copy e:\i386\ntdetect.com
here, e:\ is the CD - ROM drive
if it ask for overwrite than press "y"
than,
write exit press enter
than root from your hard disk
now window will start work
If you want more details below is the link
http://support.microsoft.com/kb/318728

Published By

S.G.Godwin Dinesh.MCA
Sr.System Administrator

A list of SCCM log Files

The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR%\SysWOW64\CCM\Logs (for x64 OS).
The SCCM server log files are located in the \Logs or SMS_CCM\Logs folder. IIS logs can be found in %WINDIR%\System32\logfiles\W3SVC1 folder.

Client Log Files

• CAS - Content Access Service. Maintains the local package cache.
• Ccmexec.log - Records activities of the client and the SMS Agent Host service.
• CertificateMaintenance.log - Maintains certificates for Active Directory directory service and management points.
• ClientIDManagerStartup.log - Creates and maintains the client GUID.
• ClientLocation.log - Site assignment tasks.
• ContentTransferManager.log - Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
• DataTransferService.log - Records all BITS communication for policy or package access.
• Execmgr.log - Records advertisements that run.
• FileBITS.log - Records all SMB package access tasks.
• Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows Management Instrumentation (WMI) provider for software inventory and file collection.
• InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software inventory records.
• LocationServices.log - Finds management points and distribution points.
• Mifprovider.log - The WMI provider for .MIF files.
• Mtrmgr.log - Monitors all software metering processes.
• PolicyAgent.log - Requests policies by using the Data Transfer service.
• PolicyAgentProvider.log - Records policy changes.
• PolicyEvaluator.log - Records new policy settings.
• Remctrl.log - Logs when the remote control component (WUSER32) starts.
• Scheduler.log - Records schedule tasks for all client operations.
• Smscliui.log - Records usage of the Systems Management tool in Control Panel.
• StatusAgent.log - Logs status messages that are created by the client components.
• SWMTRReportGen.log - Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Server Log Files

• Ccm.log - Client Configuration Manager tasks.
• Cidm.log - Records changes to the client settings by the Client Install Data Manager (CIDM).
• Colleval.log - Logs when collections are created, changed, and deleted by the Collection Evaluator.
• Compsumm.log - Records Component Status Summarizer tasks.
• Cscnfsvc.log - Records Courier Sender confirmation service tasks.
• Dataldr.log - Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
• Ddm.log - Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
• Despool.log - Records incoming site-to-site communication transfers.
• Distmgr.log - Records package creation, compression, delta replication, and information updates.
• Hman.log - Records site configuration changes, and publishes site information in Active Directory Domain Services.
• Inboxast.log - Records files that are moved from the management point to the corresponding SMS\INBOXES folder.
• Inboxmgr.log - Records file maintenance.
• Invproc.log - Records the processing of delta MIF files for the Dataloader component from client inventory files.
• Mpcontrol.log - Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
• Mpfdm.log - Management point component that moves client files to the corresponding SMS\INBOXES folder.
• MPMSI.log - Management point .msi installation log.
• MPSetup.log - Records the management point installation wrapper process.
• Ntsvrdis.log - Configuration Manager 2007 server discovery.
• Offermgr.log - Records advertisement updates.
• Offersum.log - Records summarization of advertisement status messages.
• Policypv.log - Records updates to the client policies to reflect changes to client settings or advertisements.
• Replmgr.log - Records the replication of files between the site server components and the Scheduler component.
• Rsetup.log - Reporting point setup log.
• Sched.log - Records site-to-site job and package replication.
• Sender.log - Records files that are sent to other child and parent sites.
• Sinvproc.log - Records client software inventory data processing to the site database in Microsoft SQL Server.
• Sitecomp.log - Records maintenance of the installed site components.
• Sitectrl.log - Records site setting changes to the Sitectrl.ct0 file.
• Sitestat.log - Records the monitoring process of all site systems.
• Smsdbmon.log - Records database changes.
• Smsexec.log - Records processing of all site server component threads.
• Smsprov.log - Records WMI provider access to the site database.
• SMSReportingInstall.log - Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
• SMSSHVSetup.log - Records the success or failure (with failure reason) of installing the System Health Validator point.
• Srvacct.log - Records the maintenance of accounts when the site uses standard security.
• Statmgr.log - Writes all status messages to the database.
• Swmproc.log - Processes metering files and maintains settings.

Admin Console Log Files

• RepairWizard.log - Records errors, warnings, and information about the process of running the Repair Wizard.
• ResourceExplorer.log - Records errors, warnings, and information about running the Resource Explorer.
• SMSAdminUI.log - Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files

• MP_Ddr.log - Records the conversion of XML.ddr records from clients, and copies them to the site server.
• MP_GetAuth.log - Records the status of the site management points.
• MP_GetPolicy.log - Records policy information.
• MP_Hinv.log - Converts XML hardware inventory records from clients and copies the files to the site server.
• MP_Location.log - Records location manager tasks.
• MP_Policy.log - Records policy communication.
• MP_Relay.log - Copies files that are collected from the client.
• MP_Retry.log - Records the hardware inventory retry processes.
• MP_Sinv.log - Converts XML hardware inventory records from clients and copies them to the site server.
• MP_Status.log - Converts XML.svf status message files from clients and copies them to the site server.

Mobile Device Management Log Files

• DmClientHealth.log - Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
• DmClientRegistration.log - Records registration requests from and responses to the mobile device client in Native mode.
• DmpDatastore.log - Records all the site database connections and queries made by the Device Management Point.
• DmpDiscovery.log - Records all the discovery data from the mobile device clients on the Device Management Point.
• DmpFileCollection.log - Records mobile device file collection data from mobile device clients on the Device Management Point.
• DmpHardware.log - Records hardware inventory data from mobile device clients on the Device Management Point.
• DmpIsapi.log - Records mobile device communication data from device clients on the Device Management Point.
• dmpMSI.log - Records the MSI data for Device Management Point setup.
• DMPSetup.log - Records the mobile device management setup process.
• DmpSoftware.log - Records mobile device software distribution data from mobile device clients on the Device Management Point.
• DmpStatus.log - Records mobile device status messages data from mobile device clients on the Device Management Point.
• FspIsapi.log - Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Client Log Files

• DmCertEnroll.log - Records certificate enrollment data on mobile device clients.
• DMCertResp.htm (in \temp) - Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
• DmClientSetup.log - Records client setup data on mobile device clients.
• DmClientXfer.log - Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
• DmCommonInstaller.log - Records client transfer file installation for setting up mobile device client transfer files on client computers.
• DmInstaller.log - Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
• DmInvExtension.log - Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
• DmSvc.log - Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

• CCMSetup.log - Provides information about client-based operating system actions.
• CreateTSMedia.log - Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
• DriverCatalog.log - Provides information about device drivers that have been imported into the driver catalog.
• MP_ClientIDManager.log - Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
• MP_DriverManager.log - Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
• MP_Location.log - Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
• Pxecontrol.log - Provides information about the PXE Control Manager.
• PXEMsi.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
• PXESetup.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
• Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup logs.
• SmpIsapi.log - Provides information about the state migration point Configuration Manager 2007 client request responses.
• Smpmgr.log - Provides information about the results of state migration point health checks and configuration changes.
• SmpMSI.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
• Smsprov.log - Provides information about the SMS provider.
• Smspxe.log - Provides information about the Configuration Manager 2007 PXE service point.
• SMSSMPSetup.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
• Smsts.log - General location for all operating system deployment and task sequence log events.
• TaskSequenceProvider.log - Provides information about task sequences when they are imported, exported, or edited.
• USMT Log loadstate.log - Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
• USMT Log scanstate.log - Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

• Ccmcca.log - Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
• CIAgent.log - Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log - provides more informative details on installing the software updates required for compliance.
• locationservices.log - Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
• SDMAgent.log - Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
• SMSSha.log - The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

System Health Validator Point Log Files

• Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.
• SmsSHV.log - The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
• SmsSHVADCacheClient.log - Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
• SmsSHVCacheStore.log - Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
• SmsSHVRegistrySettings.log - Records any dynamic changes to the System Health Validator component configuration while the service is running.
• SmsSHVQuarValidator.log - Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Desired Configuration Management Log Files

• ciagent.log - Provides information about downloading, storing, and accessing assigned configuration baselines.
• dcmagent.log - Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.
• discovery.log - Provides detailed information about the Service Modeling Language (SML) processes.
• sdmagent.log - Provides information about downloading, storing, and accessing configuration item content.
• sdmdiscagent.log - Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files

• Wolmgr.log - Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.
• WolCmgr.log - Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

• ciamgr.log - Provides information about the addition, deletion, and modification of software update configuration items.
• distmgr.log - Provides information about the replication of software update deployment packages.
• objreplmgr.log - Provides information about the replication of software updates notification files from a parent to child sites.
• PatchDownloader.log - Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.
• replmgr.log - Provides information about the process for replicating files between sites.
• smsdbmon.log - Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
• SUPSetup - Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
• WCM.log - Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
• WSUSCtrl.log - Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
• wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

• Change.log - Provides information about the WSUS server database information that has changed.
• SoftwareDistribution.log - Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

• CAS.log - Provides information about the process of downloading software updates to the local cache and cache management.
• CIAgent.log - Provides information about processing configuration items, including software updates.
• LocationServices.log - Provides information about the location of the WSUS server when a scan is initiated on the client.
• PatchDownloader.log - Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
• PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting policies on client computers.
• PolicyEvaluator - Provides information about the process for evaluating policies on client computers, including policies from software updates.
• RebootCoordinator.log - Provides information about the process for coordinating system restarts on client computers after software update installations.
• ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
• ScanWrapper - Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
• SdmAgent.log - Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
• ServiceWindowManager.log - Provides information about the process for evaluating configured maintenance windows.
• smscliUI.log - Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
• SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
• StateMessage.log - Provides information about when software updates state messages are created and sent to the management point.
• UpdatesDeployment.log - Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
• UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client.
• UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
• WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates.
• WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File

• WindowsUpdate.log - Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.

Published By
S.G.Godwin Dinesh.MCA
Sr.System Administrator

Know about Your Domain Server Name or IP ?

Can you tell that what is your Domain Server IP or Domain Computer Name??????
I think it is a big question but not ...

Just a few moments .......

Open "CMD"

Type a Command here

"echo %LOGONSERVER%"

Press Enter

Hey... You got your Domain Server Computer Name .....

Lets Check that is it right ???

Open RUN menu

Now type Computer Name here for Browse LAN Computer

( Example - Your Server Name -- ZUBU -- )
In Run Menu You Type

\\ZUBU

Press OK Key or Hit Enter Key

Now Check Server Default Shared Folder Name



Published By
S.G.Godwin Dinesh.MCA
Sr.System Administrator

Windows Server 2012 R2 Preview - Schema Version

I previously posted  a "quick-hitter" blog about the schema version in Windows Server 2012. 

Windows Server 2012 R2  preview was released today! The current version is 69 

I once again used ad find to quickly find the schema version.

For those that prefer to use powershell; you can also find the object version that way. 

The current (as of 25 June 2013) Active Directory Schema version table is listed below.

Windows Server 2012 R2 Preview	69
Windows Server 2012	56
Windows 2008 R2	47
Windows 2008	44
Windows 2003 R2	31
Windows 2003	30
Windows 2000	13

You can download an evaluation copy of Windows Server 2012 R2  and go start to learn and have fun.  Thanks to all the hard work put in by the many people at Microsoft that made today happen.

Published By

S.G.Godwin Dinesh.MCA

Sr.System Administrator