Some Basic Commands used for troubleshooting.!!

1) When you want to check the machine name?
Start > Run> Type "CMD" > Enter > Type "Hostname"  (Please don't use Inverted Commas)
It will show you the system name

2) How to check system was when installed and when last time rebooted?
Start > Run> Type "CMD" > Enter >Type "Systeminfo" (Please don't use Inverted Commas)
It will show you many details includes System installed date and time, Last boot date and time, Installed patches etc.

3) How to check which version of windows you having?
Start > Run > Type " Winver" (Please don't use Inverted Commas)
It will open a Small window which will be having the Details of OS version.

4) How to check how many folders are shared on a particular machine?
Start > Run> Type "CMD" > Enter >Type "Net share" (Please don't use Inverted Commas)
It will open a list of all share Folder name with the exact path also.

its done for now. Going to do some work..!! I will update some more commands soon.

Read More

Reporting queued error: faulting application iexplore.exe, version 8.0.6001.18702, faulting module mshtml.dll, version 8.0.6001.18828, fault address 0x0009b555.

I found that we were Getting the Error related to Iexplorer.exe (for IE 8.0).
I reregistered below mentioned files by (Start > CMD > Run as administrator) and Paste the below mentioned commands.

regsvr32 Mshtml.dll
regsvr32 Urlmon.dll
regsvr32 Shdocvw.dll
regsvr32 Msjava.dll
regsvr32 Actxprxy.dll
regsvr32 Oleaut32.dll
regsvr32 Browseui.dll
regsvr32 Shell32.dll

I monitored it for last 1 hour and it seems resolved now. You can try and Let me know.

Read More

Windows Update Error Code List..!!

We usually get so many errors in our Environment when we try to install windows updates.
its tough to gather all errors at one place, Finally I found an Article from Microsoft which having all Error Details which comes at the time of windows update.
You can the details of these Errrors in the Log file located in %systemroot%\windowsupdate.log

 

Error Code list of Windows update

Read More

Difference between IPv4 and IPv6

Read More

What is the difference between ESX and ESXi ?

	ESXi	ESX
Service Console	No	Yes
Installation	Fast	Slow (Comparatively to ESXi)
Health Status	Built in	Not Built in

 The Important difference you can see when you install ESXi you will get a Yellow Screen to Configure some basic settings. In ESX you will have the Black and white screen.

Click here for more details:- Difference between ESX and ESXi

Read More

Microsoft puts Office 365 in the cloud

Microsoft Launch Office 365 Yesterday. Its a Quite Good tool which offering Office,Exchange, SharePoint and Lync (Chat) which means you can work anywhere any time. Thanks to the Cloud Computing.
 Office 365 trial Download

Read More

How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 Server?

After you have successfully deployed a Folder Redirection Group Policy object (GPO) in your site, you may want to stop Folder Redirection for one or more users. However, before you try to stop Folder Redirection, you must first enable the Redirect the folder back to the local userprofile location when policy is removed Group Policy setting.

Important After you modify a GPO and enable the Redirect the folder back to the local userprofile location when policy is removed Group Policy setting, all users who you want to stop Folder Redirection must log off and then log on again. This is to make sure that the updated GPO settings are applied before you stop Folder Redirection.

To stop Folder Redirection, follow these steps:
Enable the Redirect the folder back to the local userprofile location when policy is removed Group Policy setting. To do this, follow these steps:
Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
In the Active Directory Users and Computers console tree, locate the site, domain, or organizational unit that contains the users who you want to apply the updated GPO to.
Right-click the object, such as the organizational unit, and then click Properties.
Click the Group Policy tab.
Click the GPO that contains your Folder Redirection policy setting in the Group Policy Object Links list, and then click Edit.
In the Group Policy console tree, expand User Configuration, expand Windows Settings, and then expand Folder Redirection.
Right-click Application Data, and then click Properties.
Click the Settings tab.
In the Policy Removal box, click to select the Redirect the folder back to the local userprofile location when policy is removed policy setting, and then click OK.
Repeat steps g through i for the Desktop, My Documents, and Start Menu objects.
Close the Group Policy dialog box, and then close the Properties dialog box for the object that you selected in step c.
Important All users who are affected by your GPO modification must log off and back on to any computers where they have logged on before the changes are applied. You must apply these changes to the user's computer before you go to the next step.
When all users have logged off and then logged back on, and the updated GPO for Folder Redirection has been applied, use one of the following methods to stop Folder Redirection:
Method 1: Remove the user from the organizational unit where the folder redirection GPO is applied to a different organizational unit that does not redirect folders. To do this, follow these steps:
Important Move the user accounts, do not delete the GPO.
In the console tree of Active Directory Users and Computers, right-click DomainName, and then click Find.
Click Users, Contacts, and Groups in the Find box.
Type the name of the user account, and then click Find Now.
In the Search results box, right-click the user account, and then click Move.
In the Container to move object to box, locate a security group that does not have Folder Redirection policy enabled, and then click OK.
Method 2: Modify the security properties of the GPO to deny the user or group Read permissions and Apply Group Policy permissions to that GPO. This enables other GPO's to be applied to the user, while making sure that the folder redirection policy setting is not applied. To do this, follow these steps:
Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
In the Active Directory Users and Computers console tree, right-click the organizational unit object or domain object that has the Group Policy Object whose security properties that you want to change, and then click Properties.
In the Properties dialog box for the object, click the Group Policy tab, select the GPO that you want to change from the list, and then click Properties.
In the GPO Properties dialog box, click the Security tab, and then change the permissions so that only the required users have the Read and Apply Group Policy permissions. For users where the GPO does not apply, make sure that you click to select the Deny check box for the Read and Apply Group Policy permissions. Click OK two times.

Note Make sure that Administrators have Read and Write permissions for the GPO.
After you use one of these methods, Folder Redirection will be stopped the next time that the user processes this GPO. By default, the object is cached on the user's computer and will not be updated unless another change is detected. To force an update, you must follow these additional steps:
Create or modify a GPO that applies to the computers on which users who are affected by folder redirection policies log on.
Edit the GPO.
Under Computer Configuration, expand Administrative Templates.
Under Administrative Templates, expand System.
Under System, select Group Policy.
Double-click the Folder Redirection policy processing setting
Select the Enabled option, and then click to select the second check box. (Process even if the Group Policy objects have not changed.)
Exit the Group Policy Object Editor. Make sure that this new GPO applies to computer accounts for which users are using folder redirection.
After you apply this policy change, the computers can detect the updated folder redirection policy and will honor the changes that have been made to stop using folder redirection.

Note After a Folder Redirection GPO is applied to a user profile, those Group Policy settings are retained locally on the user's computer. Group Policy settings are changed only when a new or modified GPO is applied to the user or computer.

Please refer:-
http://support.microsoft.com/kb/888203

Read More

http://whatismyipaddress.com/

To know your internet IP Simply click on above link and you will found the IP which giving you access to the Global Network(Internet).

Read More

Schedule task Getting failed on Windows Server 2008.

I found that there are many task schedulted in my windows server 2008 DC, those should run to complete some particular Job at particular time.
Today morning I found that there are some error/Information in the form of Code on task Schedular Library.
Below is the details of code which shown in Task Schedular Library. I hope it helps:-

SCHED_S_TASK_READY
0x00041300
The task is ready to run at its next scheduled time.

SCHED_S_TASK_RUNNING
0x00041301
The task is currently running.

SCHED_S_TASK_DISABLED
0x00041302
The task will not run at the scheduled times because it has been disabled.

SCHED_S_TASK_HAS_NOT_RUN
0x00041303
The task has not yet run.

SCHED_S_TASK_NO_MORE_RUNS
0x00041304
There are no more runs scheduled for this task.

SCHED_S_TASK_NOT_SCHEDULED
0x00041305
One or more of the properties that are needed to run this task on a schedule have not been set.

SCHED_S_TASK_TERMINATED
0x00041306
The last run of the task was terminated by the user.

SCHED_S_TASK_NO_VALID_TRIGGERS
0x00041307
Either the task has no triggers or the existing triggers are disabled or not set.

SCHED_S_EVENT_TRIGGER
0x00041308
Event triggers do not have set run times.

SCHED_E_TRIGGER_NOT_FOUND
0x80041309
A task's trigger is not found.

SCHED_E_TASK_NOT_READY
0x8004130A
One or more of the properties required to run this task have not been set.

SCHED_E_TASK_NOT_RUNNING
0x8004130B
There is no running instance of the task.

SCHED_E_SERVICE_NOT_INSTALLED
0x8004130C
The Task Scheduler service is not installed on this computer.

SCHED_E_CANNOT_OPEN_TASK
0x8004130D
The task object could not be opened.

SCHED_E_INVALID_TASK
0x8004130E
The object is either an invalid task object or is not a task object.

SCHED_E_ACCOUNT_INFORMATION_NOT_SET
0x8004130F
No account information could be found in the Task Scheduler security database for the task indicated.

SCHED_E_ACCOUNT_NAME_NOT_FOUND
0x80041310
Unable to establish existence of the account specified.

SCHED_E_ACCOUNT_DBASE_CORRUPT
0x80041311
Corruption was detected in the Task Scheduler security database; the database has been reset.

SCHED_E_NO_SECURITY_SERVICES
0x80041312
Task Scheduler security services are available only on Windows NT.

SCHED_E_UNKNOWN_OBJECT_VERSION
0x80041313
The task object version is either unsupported or invalid.

SCHED_E_UNSUPPORTED_ACCOUNT_OPTION
0x80041314
The task has been configured with an unsupported combination of account settings and run time options.

SCHED_E_SERVICE_NOT_RUNNING
0x80041315
The Task Scheduler Service is not running.

SCHED_E_UNEXPECTEDNODE
0x80041316
The task XML contains an unexpected node.

SCHED_E_NAMESPACE
0x80041317
The task XML contains an element or attribute from an unexpected namespace.

SCHED_E_INVALIDVALUE
0x80041318
The task XML contains a value which is incorrectly formatted or out of range.

SCHED_E_MISSINGNODE
0x80041319
The task XML is missing a required element or attribute.

SCHED_E_MALFORMEDXML
0x8004131A
The task XML is malformed.

SCHED_S_SOME_TRIGGERS_FAILED
0x0004131B
The task is registered, but not all specified triggers will start the task.

SCHED_S_BATCH_LOGON_PROBLEM
0x0004131C
The task is registered, but may fail to start. Batch logon privilege needs to be enabled for the task principal.

SCHED_E_TOO_MANY_NODES
0x8004131D
The task XML contains too many nodes of the same type.

SCHED_E_PAST_END_BOUNDARY
0x8004131E
The task cannot be started after the trigger end boundary.

SCHED_E_ALREADY_RUNNING
0x8004131F
An instance of this task is already running.

SCHED_E_USER_NOT_LOGGED_ON
0x80041320
The task will not run because the user is not logged on.

SCHED_E_INVALID_TASK_HASH
0x80041321
The task image is corrupt or has been tampered with.

SCHED_E_SERVICE_NOT_AVAILABLE
0x80041322
The Task Scheduler service is not available.

SCHED_E_SERVICE_TOO_BUSY
0x80041323
The Task Scheduler service is too busy to handle your request. Please try again later.

SCHED_E_TASK_ATTEMPTED
0x80041324
The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition.

SCHED_S_TASK_QUEUED
0x00041325
The Task Scheduler service has asked the task to run.

SCHED_E_TASK_DISABLED
0x80041326
The task is disabled.

SCHED_E_TASK_NOT_V1_COMPAT
0x80041327
The task has properties that are not compatible with earlier versions of Windows.

SCHED_E_START_ON_DEMAND
0x80041328
The task settings do not allow the task to start on demand.

Read More

Description of password-change protocols in Windows

Windows uses many different mechanisms for changing passwords. This article describes those mechanisms.
MORE INFORMATION
The supported password-change protocols are:
The NetUserChangePassword protocol
The NetUserSetInfo protocol
The Kerberos change-password protocol (IETF Internet Draft Draft-ietf-cat-kerb-chg-password-02.txt) [port 464]
Kerberos set-password protocol (IETF Internet Draft Draft-ietf-cat-kerberos-set-passwd-00.txt) [port 464]
Lightweight Directory Access Protocol (LDAP) write-password attribute (if 128-bit Secure Sockets Layer [SSL] is used)
XACT-SMB for pre-Microsoft Windows NT (LAN Manager) compatibility
Change-password operations require that the user's current password be known before the change is allowed. Set-password operations do not have this requirement, but are controlled by the Reset Password permissions on the account.

When you are using LDAP (method 5), the domain controller and the client must both be able to use 128-bit SSL to protect the connection. If the domain controller is not configured for SSL or if appropriately long keys are not available, the password-change write is denied.

An Active Directory domain controller listens for change-password requests on all of these protocols.

As stated earlier in this article, different protocols are used in different circumstances. For example:
Interoperable Kerberos clients use the Kerberos protocols. UNIX-based systems with MIT Kerberos version 5 1.1.1 can change user passwords in a Windows-based domain by using the Kerberos change-password protocol (method 3).
When a user changes his or her own password by pressing CTRL+ALT+DELETE and then clicking Change Password, Windows NT up to Windows 2003 the NetUserChangePassword mechanism (method 1) is used if the target is a domain. From Windows Vista onwards, the Kerberos change password protocol is used for domain accounts. If the target is a Kerberos realm, the Kerberos change-password protocol (method 3) is used.
Requests to change a password from computers that are running Microsoft Windows 95/Microsoft Windows 98 use XACT-SMB (method 6).
A program that uses the ChangePassword method on the Active Directory Services Interface (ADSI) IaDSUser interface first tries to change the password by using LDAP (method 5), and then by using the NetUserChangePassword protocol (method 1).
A program that uses the SetPassword method on the ADSI IaDSUser interface first tries to change the password by using LDAP (method 5), then the Kerberos set-password protocol (method 4), and then the NetUserSetInfo protocol (method 2).
The Active Directory Users and Computers snap-in uses ADSI operations for setting user passwords.

Refer to Microsoft Article:-
http://support.microsoft.com/kb/264480

Read More

how much RAM the various Windows versions and editions support?

Here's a list of how much RAM the various Windows versions and editions support (as of May 2010):

Windows NT 4.0: 4 GB
Windows 2000 Professional: 4 GB
Windows 2000 Standard Server: 4 GB
Windows 2000 Advanced Server: 8 GB
Windows 2000 Datacenter Server: 32 GB
Windows XP Professional: 4 GB
Windows Server 2003 Web Edition: 2 GB
Windows Server 2003 Standard Edition: 4 GB
Windows Server 2003 Enterprise Edition: 32 GB
Windows Server 2003 Datacenter Edition: 64 GB
Windows Vista: 4 GB
Windows Server 2008 Standard: 4 GB
Windows Server 2008 Enterprise: 64 GB
Windows Server 2008 Datacenter: 64 GB
Windows 7: 4 GB

Read More

How to install Windows 7 via USB or Pen Drive?

Yesterday I found that I need to reinstall my OS.
I want to install windows 7, I downloaded the ISO image but now i need to burn it. When I burn it on DVD rom and trying to install its taking SO much time. SO I cancelled it.
Finally I choose to Burn this ISO image to USB Drive from this tool Windows 7 USB/DVD Download Tool (http://wudt.codeplex.com/).
After Burning it to USB I connected it to my machine and Changed the BIOS boot options First to USB Device.

and its installed within 10mins... Its Great!!.. (Remember to Plugout the USB Drive after your computer restarted First time during installation)..

Read More

In WIndows 7, whenever we connect any USB Device on Some USB Ports we Got some warning messages?

I having windows 7 installed on My Laptop, Since last many months I having some issues whenever I connect any USB Device (Pen Drive, Mouse etc) I used to get some warning messages and sometimes it not works.
Yesterday I installed below mentioned hotfix and now I tested seems the issue resolved.
This Hotfix applies to a Windows 7-based computer. The computer has an Intel platform that is based on an Intel Atom Z670 processor and an Intel SM35 Express chipset. In this situation, you may experience functionality issues on full-speed and low-speed USB devices.

http://support.microsoft.com/kb/2528984

Let me know if it works for you also!!

Read More

Latest update for Ntfs.sys

Below is a Hotfix realese by Microsoft for issues related to Ntfs.sys.
whenever your Windows Server 2003 SP2 stops responding due to Ntfs.sys use this to install.

http://support.microsoft.com/kb/980361

Read More

How to prevent installation of SP1 on Windows Server 2008 R2 and Windows 7?

Just Download the Executable from the Link (www.microsoft.com/downloads/en/details.aspx?FamilyID=D7C9A07A-5267-4BD6-87D0-E2A72099EDB7) and run the EXE tool.
This will change your Registry Key (HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\DonotAllowSP) to 1.

Read More

What VMware products are available in the Virtual Infrastructure 3 Starter, Standard and Enterprise editions?

VMware Infrastructure 3 Starter edition includes:


•ESX Server 3 with the following limitations:
◦No Fiber Channel or iSCSI SAN storage
◦Cannot be deployed on a server with more than four physical CPUs or 8G of physical memory
•VirtualCenter Agent
•Virtual Machine File System (VMFS) with the following limitations:
◦Can be used on local storage only (because the version of ESX Server in VMware Infrastructure Starter does not include SAN storage)

VMware Infrastructure 3 Standard edition includes:
•ESX Server 3 (with no limitations)
•VirtualCenter Agent
•VMFS
•Virtual SMP (up to 4-way)

VMware Infrastructure 3 Enterprise edition includes:
•VMware Infrastructure 3 Standard edition plus
•VMotion
•VMware HA
•VMware DRS
•Consolidated Backup Starter

Note:- that VirtualCenter Management Server is not part of any of the above editions and needs to be purchased separately.

 
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=5357713

Read More

How to Check Health of an ESX Server?

For checking the ESX Server Health we need to connect to the ESX Server via VI Client.
Give the ESX IP address, User name - Root and the password- xxxxxx.
Once you logged in, Just go to Configuration option and there you found an option for Health Check... Here Everything should be Normal.

Read More

How to transfer FSMO Roles?

Here is the details of commands we can use to transfer the FSMO Roles.:-
C:\ntdsutil
ntdsutil:roles
fsmo maintenance: conn
server connections: connect to server
server connections:quit
fsmo maintenance: ?
fsmo maintenance: transfer schema master

Read More

What are the diffrence between WIndows Server 2003 and 2008?

1) 2008 is a combination of vista and windows 2003r2. Some new services are introduced in it



1. RODC one new domain controller introduced in it [Read-only Domain controllers.]


2. WDS (windows deployment services) instead of RIS in 2003 server


3. shadow copy for each and every folders


4.boot sequence is changed


5.installation is 32 bit where as 2003 it is 16 as well as 32 bit, that’s why installation of 2008 is faster


6.services are known as role in it


7. Group policy editor is a separate option in ads






2) The main difference between 2003 and 2008 is Virtualization, management.


2008 has more inbuilt components and updated third party drivers Microsoft introduces new feature with 2k8 that is Hyper-V Windows Server 2008 introduces Hyper-V (V for Virtualization) but only on 64bit versions. More and more companies are seeing this as a way of reducing hardware costs by running several 'virtual' servers on one physical machine. If you like this exciting technology, make sure that you buy an edition of Windows Server 2008 that includes Hyper-V, then launch the Server Manger, add Roles.






3) In Windows Server 2008, Microsoft is introducing new features and technologies, some of which were not available in Windows Server 2003 with Service Pack 1 (SP1), that will help to reduce the power consumption of server and client operating systems, minimize environmental byproducts, and increase server efficiency.


Microsoft Windows Server 2008 has been designed with energy efficiency in mind, to provide customers with ready and convenient access to a number of new power-saving features. It includes updated support for Advanced Configuration and Power Interface (ACPI) processor power management (PPM) features, including support for processor performance states (P-states) and processor idle sleep states on multiprocessor systems. These features simplify power management in Windows Server 2008 (WS08) and can be managed easily across servers and clients using Group Policies.

Read More

How to Search EFS Files and Folders?

1) Using Search


If you have lots of time on your hands or are looking for extra pain in your life, one tool you could use to find encrypted folders and files is Windows' Search functionality. By searching for *.*, you can get a list of every single folder and file on your hard drive. You then need to look through all the results for any folder or file that's highlighted in green (assuming you haven't changed the default color for EFS folders and files).
2) Using EFSinfo

A slightly better way to find EFS folders and files is to use Microsoft's EFSinfo command-line tool. You can find it in the \Support\Tools folder on the Windows Server 2003 CD-ROM. You can use this tool to find all encrypted folders and files on your computer, but it typically produces a blizzard of information that's difficult to plow through. For example, try issuing the following command at the root of your C drive

Efsinfo /S:C:

All the filenames and folder names go blasting across your screen, so it's like looking for a needle in a haystack. You can display only those lines that contain the string ": Encrypted" by running the command

Efsinfo /S:C:  Find ": Encrypted"

Now you at least get some filtered results such as
EFS-Test.txt: Encrypted
EFS-Test: Encrypted

But, sadly, the results don't include the paths to the encrypted folders and files. (Maybe a newer version of the EFSinfo tool does, but I couldn't get the version I was using to give up this information.)

3) Using Cipher

A more suitable way to find encrypted folders and files is to use Cipher. This powerful command-line utility has many encryption and decryption options for managing the encryption environment. You can also use it to determine whether any encrypted files exist on your computer. For example, the command

Cipher /U /N

checks for encrypted files on your computer and displays any it finds. As these results show
Encrypted File(s) on your system:

C:\Program Files\EFS-Test.txt

the file's full path is included. However, in all the tests I conducted in Windows 7, the results didn't include the empty encrypted folder.

4) Using EFS-Find.vbs


When you can't get off-the-shelf tools to do exactly what you want, it's time to see what good old VBScript can do. That's how EFS-Find.vbs came into being. EFS-Find.vbs locates all encrypted folders and files on your hard disk and automatically saves their complete paths to a log file.

You can download EFS-Find.vbs by going to the Link (http://www.windowsitpro.com/article/security/A-Fast-Way-to-Find-EFS-Folders-and-Files/3.aspx) and clicking on the Download the Code Here button (The file will be named 129393.zip). Save the script to a location on your computer (in this example, C:\Test\EFS-Find.vbs), then open a command prompt window as an administer and run the command

Cscript //NOLOGO C:\Test\EFS-Find.vbs

The script will search all the local hard drives on your computer and report on any EFS folders and files it finds. Unlike the Cipher /U /N command, EFS-Find.vbs reports on any empty encrypted folders.

Besides displaying a summary report on screen, the script displays the log file's name, which is in the format EFS-Find-%COMPUTERNAME%.txt. This naming convention makes it easy to distinguish between different computers if you need to push the files to a central location without them being overwritten. The log file is saved to the directory specified in the %TEMP% environment variable, which is usually the current user's temporary folder.

Here's how EFS-Find.vbs works. It begins by making sure that you're a local administrator so that it can run properly. Then, for each fixed drive, it performs two checks. First, it checks each folder to see if it's encrypted. It does this by taking advantage of Windows Management Instrumentation's (WMI's) Win32_Directory class. Second, it checks each file to see if it's encrypted using WMI's CIM_DataFile class. The script writes the results to the log file, which it opens before quitting. If you aren't running the script interactively, you can disable this feature. Find the code

objShell.Run



" _

& strLogFileName &



"

and comment it out.



The script also writes information to the registry at HKLM\SOFTWARE\EFS-Find. That way, there's always a fixed location to query the computer about the script's status. In addition, you can be certain of the computer's encryption status on that particular date.


EFS-Find.vbs returns an error level that you can check if desired. Simply execute the following command in the same command prompt window you used to run the script



ECHO %ERRORLEVEL%

An error level of 10 indicates the script exited because it wasn't run under elevated permissions (i.e., as an administrator). An error level of 999 indicates at least one EFS folder or file was detected. If the script returns an error level of 0, no EFS folders or files were detected.

If the script detects EFS folders and files, you can navigate to them using the paths provided in the log file and decrypt or remove them. Afterward, you can rerun EFS-Find.vbs and the error level check to confirm that no EFS folders or files exist.

Read More

How to check the Windows Version installed in your machine?

To check the Version, go to Start > Run > Type "Winver" and Press Enter.
You will get the details.

Read More

Interview Questions asked for System Administrator Position!

As far my 7years journey I have many interviews with many good reknown companies i.e. HP, IBM,Microsoft.
Here is a List of some questions (which i can remember ) asked to me in Either Telephonic or F2F interview:-
1) What is Active Directory?
2) What is Active Directory Database?
3) What is DNS?
4) What are different type of DNS records?
5) What are different type of DND scopes?
6) What you understand from DHCP?
7) How DHCP works?
8) What is the difference between the WINS and DNS?
9) How to Compact Active Directory?
10) How to Defragment Active Directory database? How many types of Defreagment available?
11) What is DHCP? and where is the Database stored?
12) What is Stub Zone?
13) 5 Major Difference between windows 2003 and windows 2008?
14) Port no of DHCP server? - DHCP server listens at 67 and responds at 68.

Read More

Windows 7 and Windows Server 2008 R2 SP1

Microsoft launched the SP1 for Win 7 and windows 2008 R2.
Please download it from below link:-
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c3202ce6-4056-4059-8a1b-3a9b77cdfdda

Read More

How to check Last time when your machine restarted?

To know the details about when was last time your Server / Machine restarted you can either use the command "Systeminfo" or you can right click on your network connections. It will give you how many days since your Server / machine is UP.

Read More

What is SVCHOST.exe in Task manager?

Many time we opend the task manager to see the performance of the machine we found that there is a Process called SVCHOST.exe is using some of the resources.
Svchost.exe is a generic host process name for services that run from dynamic-link libraries (DLLs).In General language its a Combination of many services in one file.
The Svchost.exe file is located in the %SystemRoot%\System32 folder. At startup, Svchost.exe checks the services part of the registry to construct a list of services that it must load. Multiple instances of Svchost.exe can run at the same time. Each Svchost.exe session can contain a grouping of services. Therefore, separate services can run, depending on how and where Svchost.exe is started. This grouping of services allows for better control and easier debugging.

Svchost.exe groups are identified in the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Svchost
Each value under this key represents a separate Svchost group and appears as a separate instance when you are viewing active processes. Each value is a REG_MULTI_SZ value and contains the services that run under that Svchost group. Each Svchost group can contain one or more service names that are extracted from the following registry key, whose Parameters key contains a ServiceDLL value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Service

To view the list of services that are running in Svchost:


Click Start on the Windows taskbar, and then click Run.

In the Open box, type CMD, and then press ENTER.

Type Tasklist /SVC, and then press ENTER.

Tasklist displays a list of active processes. The /SVC switch shows the list of active services in each process.

Read More

List of the updates including in "ShadowProtect version 3.5.2" (19 March 2010)!!

• A workaround has been added to resolve a system-induced blue screen (BSOD) which occurred on Windows Server 2008R2 with Hyper-V at the start of a ShadowProtect backup.




• A fix has been made to eliminate a system-wide hang/deadlock which could occur on Windows Server 2008 at the start of a ShadowProtect backup.



• A fix has been made to eliminate a hung ShadowProtect backup job which could occur on Windows Server 2008 when at the start of a ShadowProtect backup.



• A fix has been made to resolve rare situations where VDiff (the fast incremental tracking) could not be enabled for some volumes.



• A fix has been made to the ShadowProtect NT service (ShadowProtectSvc.exe) so that when it is automatically woken up from sleep mode it will take the next backup if a scheduled backup was missed while the machine was asleep. In versions prior to 3.5.2, the missed backup would only be taken if the machine was manually woken up, but not when it was automatically woken up.



• A fix has been made to the installed ShadowProtect components to resolve an issue where a new manual differential image, immediately dependent upon an existing full image file, would not be created with the same compression and encryption settings as the full image file (as it should be).



• A fix has been made to the image.exe .MD5 text file processing code to properly process all possible text file types (ANSI, Unicode little-endian with preamble/BOM, Unicode little-endian without preamble/BOM, Unicode big-endian with preamble/BOM, Unicode big-endian without preamble/BOM, UTF-8 with preamble/BOM, UTF-8 without preamble/BOM).



• A fix has been made to the recovery enviornment post-restore code to preserve the drive letter of a restored OS volume. In the past this has been (and still is) done automatically as part of the post-restore HIR process. But in situations where the restore process did not involve HIR, the drive letter of the resored OS volume was not preserved. Now, regardless whether or not the restore uses HIR, if you are restoring an image of an OS volume then after the restore finishes the proper changes will be made to preserve that OS volume's drive letter when that OS volume is booted.



• A fix has been made to the post-restore BCD patching code to properly deal with hidden recovery partitions (such as the Win7 recovery partition).

Read More

How can I check the version of my System Center Configuration Manager (SCCM) 2007 installation?

There are now several different versions of SCCM 2007—RTM, SP1, SP2, R2, and R3. If you launch the SCCM administration console and select Help, About System Center Configuration Manager, you can check the version. The versions and their numbers are:

•RTM - 4.00.5931.0000
•SP1 - 4.00.6221.1000
•SP2 - 4.00.6487.2000
To check if you're using R2 or R3, open the properties of the SCCM site. The General tab once again shows the version, but also shows if R2 or R3 are installed, as shown here:

Read More

Article ID: 2487376

Microsoft releases a fix for Stop error when you replace an iSCSI network adapter or a motherboard by using an identical device on a Windows Server 2008-based or Windows Vista-based computer: "0x0000007B"


Please visit :-
http://www.mskbarticles.com/index.php?kb=2487376
and download the Hotfix.

Read More

SFC (System File Checker)

System File Checker gives an administrator the ability to scan all protected files to verify their versions. If System File Checker discovers that a protected file has been overwritten, it retrieves the correct version of the file from the cache folder (%Systemroot%\System32\Dllcache) or the Windows installation source files, and then replaces the incorrect file. System File Checker also checks and repopulates the cache folder. You must be logged on as an administrator or as a member of the Administrators group to run System File Checker. If the cache folder becomes damaged or unusable, you can use the sfc /scannow, the sfc /scanonce, or the sfc /scanboot commands to repair its contents.
Back to the top
System File Checker Tool Syntax
Sfc [/Scannow] [/Scanonce] [/Scanboot] [/Revert] [/Purgecache] [/Cachesize=x]
/Scannow: Scans all protected system files immediately and replaces incorrect versions with correct Microsoft versions. This command may require access to the Windows installation source files.
/Scanonce: Scans all protected system files one time when you restart your computer. This command may require access to the Windows installation source files when you restart the computer. The SfcScan DWORD value is set to 2 in the following registry key when you run this command:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
/Scanboot: Scans all protected system files every time you start your computer. This command may require access to the Windows installation source files every time you start your computer. The SfcScan DWORD value is set to 1 in the following registry key when you run this command:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
/Revert: Returns scan to the default setting (do not scan protected files when you start the computer).The default cache size is not reset when you run this command. This command is equivalent to the /Enable switch in Windows 2000.
/Purgecache: Purges the file cache and scans all protected system files immediately. This command may require access to the Windows installation source files.
/Cachesize=x: Sets the file cache size to x megabytes (MB). The default size of the cache is 50 MB. This command requires you to restart the computer, and then run the /purgecache command to adjust the size of the on-disk cache. This command sets the SfcQuota DWORD value to x in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Read More

How to determine the page file size in 64bit servers?

The 64-bit versions of Microsoft Windows Server 2003 and Microsoft Windows XP can support more RAM than the 32-bit versions of these products. When lots of memory is added to a computer, a paging file may not be required. When you use the Pages/sec counter to measure paging file use, the value that is returned may not be accurate. To obtain an accurate measurement of paging file use, you must also use other performance counters. You can use System Monitor measurements to calculate the size of the paging file that your computer requires.

Windows Domain Controllers and DFS Replication, Certificate and ADAM/LDS Servers are not supported without a configured pagefile. Because the algorithm the LSASS database cache depends on the "transition pages repurposed/second" perfmon counter, a pagefile is required to make sure that the database cache is capable to release memory if memory is requested by other services or applications.
Back to the top
INTRODUCTION
When you set up a 64-bit version of Microsoft Windows Server 2003 or Microsoft Windows XP, the operating system will create a page file that is one and a half times the amount of RAM that is installed in your computer. However, as the amount of RAM in a computer increases, the need for a page file decreases. The following guidelines and methods will help you determine the appropriate page file size for your system.
Back to the top
Comparison of memory and CPU limits in the 32-bit and 64-bit versions of Windows
When you set up a 32-bit version or a 64-bit version of Windows Server 2003 or Windows XP, a page file is created that is one and a half times the amount of RAM that is installed in the computer provided there is sufficient free space on the system hard disk. However, as more RAM is added to a computer, the need for a page file decreases. If you have enough RAM installed in your computer, you may not require a page file at all, unless one is required by a specific application.

The following chart illustrates the amount of RAM and the number of CPUs that can be installed on a computer depending on the operating system that is installed. RAM and CPU limits are much larger in 64-bit operating systems than in 32-bit operating systems.
Collapse this tableExpand this table
General memory limits 32-bit 64-bit
Total virtual address space 4 gigabytes (GB) 16 terabytes
Virtual address space per 32-bit process 2 GB, 3 GB if the system is booted with the /3GB switch 2 GB, 4 GB if the application is compiled with the /LARGEADDRESSAWARE switch
Virtual address space per 64-bit process Not applicable 8 terabytes
Paged pool 470 megabytes (MB) 128 GB
Non-paged pool 256 MB 128 GB
System cache 1 GB 1 terabyte

Collapse this tableExpand this table
Physical memory and CPU limits 32-bit 64-bit
Windows XP Professional 4 GB / 1-2 CPUs 128 GB / 1-2 CPUs
Windows Server 2003, Standard Edition 4 GB / 1-4 CPUs 32 GB / 1-4 CPUs
Windows Server 2003, Enterprise Edition 64 GB / 1-8 CPUs 1 terabyte / 1-8 CPUs
Windows Server 2003, Datacenter Edition 64 GB / 1-32 CPUs 1 terabyte / 1-64 CPUs
Windows Server 2003 SP1, Enterprise Edition 64 GB / 1-8 CPUs 1 terabyte / 1-8 CPUs
Windows Server 2003 SP1, Datacenter Edition 64 GB / 1-32 CPUs 1 terabyte / 1-64 CPUs

There is no specific recommendation for page file size. Your requirements will be based on the hardware and software that you use and the load that you put on the computer. To monitor page file usage and requirements, run System Monitor, and gather a log during typical usage conditions. Focus on the following counters.
Collapse this tableExpand this table
Counter threshold Suggested value
Memory\\Available Bytes No less than 4 MB
Memory\\Pages Input/sec No more than 10 pages
Paging File\\% Usage No more than 70 percent
Paging File\\% Usage Peak No more than 70 percent
Process\\Page File Bytes Peak Not applicable

Note Page file use should be tracked periodically. When you increase the use or the load on the system, you generally increase the demand for virtual address space and page file space.
Back to the top
The Pages/sec counter
When you use System Monitor, the values that are returned by the Pages/sec counter for the Memory performance object may be more than you expect. These values may not be related to either paging file activity or cache activity. Instead, these values may be caused by an application that is sequentially reading a memory-mapped file.

The Pages/sec counter counts the number of pages that are read from the disk or that are written to the disk to resolve memory references to pages. These pages were not in memory at the time of the reference. The Pages/sec value is the sum of the Pages Input/sec and Pages Output/sec counter values. The Pages/sec counter includes paging traffic on behalf of the system cache to access file data for applications.

Pages/sec is the primary counter to watch if you are concerned about excessive memory pressure (thrashing) and the excessive paging that may result.

However, the Pages/sec counter also accounts for other activity, such as the sequential reading of memory-mapped files that are either cached or not. Typically, the Pages/sec counter is counting other activity when you see the following:
A high value for the Memory: Pages/sec counter.
An average value, relative to the system being monitored, or a high value for the Memory: Available Bytes counter.
An average or small value for the Paging File: % Usage counter.
For a non-cached memory-mapped file, you also see average or low cache activity. (Low cache activity is also known as cache fault activity.)
Therefore, a high value for the Memory: Pages/sec counter does not necessarily indicate memory pressure or a System Monitor reporting error. To gain an accurate reading of your system, you must also monitor other counters.
Back to the top
How to calculate page file size
Use one or more of the following methods to help you calculate page file size.
Method 1: Use performance logs to understand the paging activity on your computer
Click Start, point to Administrative Tools, and then click Performance.
Expand Performance Logs and Alerts, click Counter Logs, right-click the blank space in the right-pane, and then click New Log Settings.
In the Name box, type a name for the log, and then click OK.
On the General tab, click Add Counters.
Click Use local computer counters.
In the Performance object list, click Paging File.
Click Select counters from list, click % Usage, and then click Add.
In the Performance object list, click Memory.
In Select counters from list, click Available Bytes, and then click Add.
In Select counters from list, click Pages Input/sec, click Add, and then click Close.
Click OK.
Use the log that you collect during typical computer use to understand the paging activity on your computer. Then, adjust the page file size accordingly.
Method 2: Use the Page File Bytes Peak counter to calculate page file size
Click Start, point to Administrative Tools, and then click Performance.
Click System Monitor.
In the right pane, click + (the Add button).
Click Use local computer counters.
In the Performance object list, click Process.
Click Select counters from list, click Page File Bytes Peak, click Add, and then click Close.
Let the counter run during typical use of your computer.
Note the maximum value for the Page File Bytes Peak counter, and then multiply the value by 0.70. The sum of the equation is the size to set for your page file.
Method 3: Calculate the minimum and maximum page file size
To determine the approximate minimum page file that is required by your system, calculate the sum of peak private bytes that are used by each process on the system. Then, subtract the amount of memory on the system.

To determine the approximate maximum page file space that is required for your system, calculate the sum of peak private bytes that are used by each process on the system. Then, add a margin of additional space. Do not subtract the amount of memory on the system. The size of the additional margin can be adjusted based on your confidence in the snapshot data that is used to estimate page file requirements.

Note This estimate is accurate only if the snapshot of data that is used to make the calculations is accurate.
Back to the top
Page file input/output rates
To avoid overloading the system or other disks with page input/output (I/O) activity, use the following guidelines when you set up the page file on your computer:
If the page I/O (real disk I/O) rate is more than 10 pages per second, we recommend that you do not put the page file where the I/O activity occurs on the system disk. When the page I/O rate is 10 pages per second or more, we recommend that you dedicate a separate hard disk for paging.
If the page I/O rate to a particular disk that is used for paging is more than 60 disk I/O operations per second, use more than one dedicated page hard disk to obtain better performance. To do this, use multiple non-striped disks for paging, or use raid 0 striped disks for paging. Dedicate approximately one I/O hard disk to paging for every 60 pages per second of I/O activity.

For example, if a system is averaging 150 pages of I/O activity per second, use three individual hard disks, or a three-disk raid 0 stripe set for the page file.

Note These estimates are for hard disks that run at 7200 revolutions per minute (rpm). If you use a hard disk that runs faster, the I/O rate a disk can handle for page I/O will increase.

Note If peak performance is critical to your system, use peak I/O rates instead of average I/O rates for these calculations.
Important Supportability Information: This article is specifically for computers that do not need kernel mode or full memory dump analysis. For business-critical servers where business processes require to server to capture physical memory dumps for analysis, the traditional model of the page file should be at least the size of physical ram plus 1 MB, or 1.5 times the default physical RAM. This makes sure that the free disk space of the operating system partition is large enough to hold the OS, hotfixes, installed applications, installed services, a dump file, and the page file. On a server that has 32 GB of memory, drive C may have to be at least 86 GB to 90 GB. This is 32 GB for memory dump, 48 GB for the page file (1.5 times the physical memory), 4 GB for the operating system, and 2 to 4 GB for the applications, the installed services, the temp files, and so on. Remember that a driver or kernel mode service leak could consume all free physical RAM. Therefore, a Windows Server 2003 x64 SP1-based server in 64-bit mode with 32GB of RAM could have a 32 GB kernel memory dump file, where you would expect only a 1 to 2 GB dump file in 32-bit mode. This behavior occurs because of the greatly increased memory pools.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
294418 (http://support.microsoft.com/kb/294418/ ) Comparison of 32-bit and 64-bit memory architecture for 64-bit editions of Windows XP and Windows Server 2003
Back to the top
MORE INFORMATION
Technical support for x64-based versions of Microsoft Windows
If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you must have technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

For product information about Windows XP Professional x64 Edition, visit the following Microsoft Web site:
http://www.microsoft.com/windowsxp/64bit/default.mspx (http://www.microsoft.com/windowsxp/64bit/default.mspx)
For product information about x64-based versions of Windows Server 2003, visit the following Microsoft Web site:
http://www.microsoft.com/windowsserver2003/64bit/x64/default.mspx (http://www.microsoft.com/windowsserver2003/64bit/x64/default.mspx)
Back to the top

--------------------------------------------------------------------------------

APPLIES TO
Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
Microsoft Windows Server 2003, Standard x64 Edition
Microsoft Windows Server 2003, Datacenter x64 Edition
Microsoft Windows Server 2003, Enterprise x64 Edition
Microsoft Windows XP Professional x64 Edition

http://www.mskbarticles.com/index.php?kb=889654

Read More

Default Replication Interval

Default replication intervals are five minutes between domain controllers in the same site, and once every three hours between domain controllers in different sites (minimum 15 minutes).

REPADMIN /SHOWREPS %UPSTREAMCOMPUTER%
REPADMIN /SHOWREPS %DOWNSTREAMCOMPUTER%

Read More

what is Active Directory!!

Windows 2000 Active Directory data store, the actual database file, is %SystemRoot%\ntds\NTDS.DIT. The ntds.dit file is the heart of Active Directory including user accounts. Active Directory's database engine is the Extensible Storage Engine ( ESE ) which is based on the Jet database used by Exchange 5.5 and WINS. The ESE has the capability to grow to 16 terabytes which would be large enough for 10 million objects. Back to the real world. Only the Jet database can maniuplate information within the AD datastore.
For information on domain controller configuration to optimize Active Directory, see Optimize Active Directory Disk Performance

The Active Directory ESE database, NTDS.DIT, consists of the following tables:

Schema table
the types of objects that can be created in the Active Directory, relationships between them, and the optional and mandatory attributes on each type of object. This table is fairly static and much smaller than the data table.
Link table
contains linked attributes, which contain values referring to other objects in the Active Directory. Take the MemberOf attribute on a user object. That attribute contains values that reference groups to which the user belongs. This is also far smaller than the data table.
Data table
users, groups, application-specific data, and any other data stored in the Active Directory. The data table can be thought of as having rows where each row represents an instance of an object such as a user, and columns where each column represents an attribute in the schema such as GivenName.
From a different perspective, Active Directory has three types of data

Schema information
definitional details about objects and attributes that one CAN store in the AD. Replicates to all domain controllers. Static in nature.
Configuration information
configuration data about forest and trees. Replicates to all domain controllers. Static as your forest is.
Domain information
object information for a domain. Replicates to all domain controllers within a domain. The object portion becomes part of Global Catalog. The attribute values (the actual bulk of data) only replicates within the domain.
Although GUIDs are unique, they are large. AD uses distinguished name tag ( DNT ). DNT is a 4-byte DWORD value which is incremented when a new object is created in the store. The DNT represents the object's database row number. It is an example of a fixed column. Each object's parent relationship is stored as a parent distinguished name tag ( PDNT ). Resolution of parent-child relationships is optimized because the DNT and PDNT are indexed fields in the database. For more technical info on the AD datastore and its organization, a good starting point is the Active Directory Database Sizing document.

The size of ntds.dit will often be different sizes across the domain controllers in a domain. Remember that Active Directory is a multi-master independent model where updates are occuring in each of the ADs with the changes being replicated over time to the other domain controllers. The changed data is replicated between domain controllers, not the database, so there is no guarantee that the files are going to be the same size across all domain controllers.

Active Directory routinely performs online database defragmentation, but this is limited to the disposal of tombstoned objects. The database file cannot be compacted while Active Directory is mounted. An ntds.dit file that has been defragmented offline ( compacted ), can be much smaller than the ntds.dit file on its peers. To defrag ntds.dit offline:

Back up the Active Directory using Windows 2000 Backup. W2K backup natively supports backing up Active Directory while online. This occurs automatically when you select the option to back up everything on the computer in the Backup Wizard, or independently by selecting to back up System State in the backup wizard.
Reboot
Select the appropriate installation from the boot menu, and press F8 to display the Windows 2000 Advanced Options menu.
Choose Directory Services Restore Mode and press ENTER. Press ENTER again to start the boot process.
Logon using the password defined for the local Administrator account in the offline SAM.
Click Start, Programs, Accessories, and then click Command Prompt.
At the command prompt, run the ntdsutil command.
When ntdsutil has started
Type files and press ENTER.
Type info and then press ENTER. This will display current information about the path and size of the Active Directory database and its log files.
Type compact to drive:\directory, and press ENTER. Be sure that the drive specified has enough drive space for the compacted database to be created. I know, you don't know how big the compacted version will be, but if there is enough space for the uncompacted version, you should be OK. A gotcha!: You must specify a directory path and if the path name has spaces, the command will not work unless you use quotation marks
compact to "c:\my new folder"

Type quit and press Enter.
Type quit and press Enter to return to the command prompt. A new compacted database named Ntds.dit can be found in the folder you specified.
Copy the new ntds.dit file over the old ntds.dit file. You have successfully compacted the Active Directory database. If you believe in belts and suspenders, I would copy the old uncompacted database somewhere else before I overwrote it with the new compacted version.
Reboot and see if all is normal.
This is a server by server task. Monitor the size of ntds.dit and if it starts growing and performance is slow and you can not see why either situation should apply, consider offline defrags.
If ntds.dit gets corrupted or deleted or is missing ( can happen if the promotion process to domain controller goes bad ), you have to manually recover it using Windows 2000 Backup. Now you did do W2K backups right?:

Reboot the domain controller and press F8 to display the Windows 2000 Advanced Options menu.
Select Directory Services Restore Mode and then press ENTER.
Select the correct installation, and then press ENTER to start the boot process.
Logon using the administrator account and password you specified during the promotion process. When you ran Dcpromo.exe to install Active Directory, it requested a password to be used for the Administrator password for Active Directory Restore Mode. This password is not stored in Active Directory. It is stored in an NT4-style SAM file and is the only account available when the AD is corrupted.
Click OK. This acknowledges the warning message that you are using Safe mode.
Click Start, Programs, Accessories, System Tools, and then click Backup.
Select the Restore tab.
Click the + symbol next to the following items to expand them:
File
Media Created
System Drive
Winnt
NTDS
Click the NTDS folder to display the files in the folder.
Click to select the ntds.dit check box.
Leave the Restore files to box set to Original Location. This check box provides the option to restore to an alternative location. If you restore to an alternative location, you will have to copy the ntds.dit file into the %SystemRoot%\ntds folder.
Click Start Restore.
To move a database or log file :

Reboot the domain controller and press F8 to display the Windows 2000 Advanced Options menu.
Select Directory Services Restore Mode and then press ENTER.
Select the correct installation, and then press ENTER to start the boot process.
Logon using the administrator account and password you specified during the promotion process. When you ran Dcpromo.exe to install Active Directory, it requested a password to be used for the Administrator password for Active Directory Restore Mode. This password is not stored in Active Directory. It is stored in an NT4-style SAM file and is the only account available when the AD is corrupted.
Start a command prompt, and then type ntdsutil.exe .
At a Ntdsutil prompt, type files.
At the File Maintenance prompt
To move a database, type move db to %s
where %s is the drive and folder where you want the database moved.
To move log files, type move logs to %s
where %s is the drive and folder where you want the log files moved.
To view the log files or database, type info.
To verify the integrity of the database at its new location, type integrity.
Type quit
Type quit to return to a command prompt.
Restart the computer in Normal mode.
When you move the database and log files, you must back up the domain controller

Read More