- Boot onto DVD of Windows Server 2008
- Choose “Repair your computer”
- Launch cmd
- Go to c:\windows\system32
- Rename Utilman.exe to Utilman.exe.bak
- Copy cmd.exe to Utilman.exe
- Reboot on Windows
- Do the keyboard shortcut Windows + U when on the logon screen
- net user administrator Newpass123 inside the cmd
- log on with the domain admin account and this new pass
- change the password to remember it if needed
- Reboot on the DVD to put back the original Utilman.exe
Showing posts with label Windows Server 2008. Show all posts
Showing posts with label Windows Server 2008. Show all posts
Monday, December 12, 2011
How to reset domain admin password on a Windows Server 2008
Friday, October 21, 2011
How to add a DSRM startup option in Windows Server 2008 R2
From this blog post we should open an administrator command prompt and enter these lines:
bcdedit /copy {current} /d "Directory Services Restore Mode"
bcdedit /set {GUID} safeboot dsrepair
bcdedit /timeout 10
where {GUID} is the result of the first command.
bcdedit /copy {current} /d "Directory Services Restore Mode"
bcdedit /set {GUID} safeboot dsrepair
bcdedit /timeout 10
where {GUID} is the result of the first command.
Friday, October 14, 2011
Troubleshooting "The RPC server is unavailable"
Please read the following article from Microsoft Technet Wiki
Monday, July 25, 2011
USN and USN Rollback
Please read the following articles from Microsoft:
USN and USN Rollback
How to detect and recover from a USN rollback in Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2
Force Domain Controller Removal
Clean Up Server Metadata
USN and USN Rollback
How to detect and recover from a USN rollback in Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2
Force Domain Controller Removal
Clean Up Server Metadata
Thursday, January 13, 2011
How to connect to a SMB share in a Windows Server using an alias name
According to this Microsoft article when a client computer connects to a Microsoft Windows 2000-based computer or a Microsoft Windows Server 2003-based computer by using an alias name, the client may receive the following error message:
System error 52 has occurred.
A duplicate name exists on the network.
This problem can occur when you try to connect to the server by using a CNAME alias that is created in the DNS zone. For example, this problem may occur with a command similar to the following sample command
net view \\alias.domain name.com
where alias is a CNAME record that is created for the server in the domain name.com zone. The server is not "listening" on the alias, and therefore is not accepting connections to that name.
To resolve this problem in Windows Server 2003, follow these steps:
1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
2. Apply the following registry change to the file server. To do so, follow these steps:
1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
4. Quit Registry Editor.
3. Restart your computer.
You may also have to set the SPN (Service Principal Name) for the Alias Name:
setspn -a host/aliasname targetserver
setspn -a host/aliasname.contoso.com targetserver
The registry key that is mentioned is applicable only to SMB 1.0. To communicate over the SMB2.0 protocol, or CIFS (Common Internet File System), you do not have to set the registry key. SMB 2.0 allows for the functionality described in this article to work by default without additional configuration. Computers that run Windows Server 2008, Windows Server 2008 R2, Windows Vista, and Windows 7 support both SMB 1.0 and SMB 2.0. Windows includes an SMB client component (Client for Microsoft Windows) and an SMB server component (File and Printer Sharing for Microsoft Windows). By default, SMB 2.0 is the file sharing protocol that is used when both client and server support it.
The SMB protocol revision to be used for file operations is decided during the negotiation phase. A Windows Vista or later client advertises to the server that it understands the new SMB 2.0 protocol. If the server understands SMB 2.0, SMB 2.0 is used for communication. Otherwise, the client and server use SMB 1.0. If SMB 1.0 is expected to be used, you can set the registry key that is mentioned above on Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7.
System error 52 has occurred.
A duplicate name exists on the network.
This problem can occur when you try to connect to the server by using a CNAME alias that is created in the DNS zone. For example, this problem may occur with a command similar to the following sample command
net view \\alias.domain name.com
where alias is a CNAME record that is created for the server in the domain name.com zone. The server is not "listening" on the alias, and therefore is not accepting connections to that name.
To resolve this problem in Windows Server 2003, follow these steps:
1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
2. Apply the following registry change to the file server. To do so, follow these steps:
1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
4. Quit Registry Editor.
3. Restart your computer.
You may also have to set the SPN (Service Principal Name) for the Alias Name:
setspn -a host/aliasname targetserver
setspn -a host/aliasname.contoso.com targetserver
The registry key that is mentioned is applicable only to SMB 1.0. To communicate over the SMB2.0 protocol, or CIFS (Common Internet File System), you do not have to set the registry key. SMB 2.0 allows for the functionality described in this article to work by default without additional configuration. Computers that run Windows Server 2008, Windows Server 2008 R2, Windows Vista, and Windows 7 support both SMB 1.0 and SMB 2.0. Windows includes an SMB client component (Client for Microsoft Windows) and an SMB server component (File and Printer Sharing for Microsoft Windows). By default, SMB 2.0 is the file sharing protocol that is used when both client and server support it.
The SMB protocol revision to be used for file operations is decided during the negotiation phase. A Windows Vista or later client advertises to the server that it understands the new SMB 2.0 protocol. If the server understands SMB 2.0, SMB 2.0 is used for communication. Otherwise, the client and server use SMB 1.0. If SMB 1.0 is expected to be used, you can set the registry key that is mentioned above on Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7.
Thursday, September 9, 2010
How to configure pagefile in windows 2008 Server Core
From http://www.hyper-v.nu/blogs/jaapwess/?p=41 we read:
To configure the pagefile on a Hyper-V Server Core or Hyper-V Server you can use the following commands:
wmic computersystem set AutomaticManagedPagefile=False
wmic pagefileset where name="c:\\pagefile.sys" set InitialSize=4000,MaximumSize=6000
It is possible to check the pagefile settings using the following command:
wmic pagefile get /format:list
To configure the pagefile on a Hyper-V Server Core or Hyper-V Server you can use the following commands:
wmic computersystem set AutomaticManagedPagefile=False
wmic pagefileset where name="c:\\pagefile.sys" set InitialSize=4000,MaximumSize=6000
It is possible to check the pagefile settings using the following command:
wmic pagefile get /format:list
Thursday, July 29, 2010
Hyper-V backup can cause slow system boot / large registry files
There is a bug in Windows 2008 and Windows 2008 R2. The startup time increases every time after you back up the data on all the disks of the computer in Windows Server 2008 R2, if the computer runs some virtual machines. For more details and a hotfix look at this KB article from Microsoft
http://support.microsoft.com/kb/982210
Also take a look at these posts
http://blogs.msdn.com/b/virtual_pc_guy/
http://garysgambit.blogspot.com/2010/05/windows-2008-hyper-v-vss-backup-bug.html
http://virtuallyaware.spaces.live.com/
http://support.microsoft.com/kb/982210
Also take a look at these posts
http://blogs.msdn.com/b/virtual_pc_guy/
http://garysgambit.blogspot.com/2010/05/windows-2008-hyper-v-vss-backup-bug.html
http://virtuallyaware.spaces.live.com/
Wednesday, July 21, 2010
Friday, June 18, 2010
How to add multiple NetBIOS names to Windows servers
You can add another NetBIOS name in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
section of the Windows registry by adding the
OptionalNames string value.
If three or more NetBIOS names are required, use the multi-string value with the same name.
This NetBIOS name is not treated the same as the server’s "primary" name. To aid in name resolution add a DNS CNAME record that points to the server’s primary name.
For more info take a look at http://blogs.techrepublic.com.com/datacenter/?p=2593&tag=nl.e071
Another interesting post about this theme is the following:
Multiple names for one computer from Jose Barreto's blog
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
section of the Windows registry by adding the
OptionalNames string value.
If three or more NetBIOS names are required, use the multi-string value with the same name.
This NetBIOS name is not treated the same as the server’s "primary" name. To aid in name resolution add a DNS CNAME record that points to the server’s primary name.
For more info take a look at http://blogs.techrepublic.com.com/datacenter/?p=2593&tag=nl.e071
Another interesting post about this theme is the following:
Multiple names for one computer from Jose Barreto's blog
Registry settings for folder redirection in Windows
Read the following link from Microsoft:
http://support.microsoft.com/kb/242557
http://support.microsoft.com/kb/242557
Thursday, April 29, 2010
Sunday, April 25, 2010
Antivirus scan exclusions
Read this blog post: http://blogs.technet.com/b/jeff_stokes/archive/2010/05/19/anti-virus-exclusions-and-you.aspx
Read also the following links:
http://myitforum.com/cs2/blogs/scassells/archive/2007/05/14/what-anti-virus-scanning-exclusions-should-be-considered-for-system-and-servers.aspx
http://www.hypervizor.net/2010/03/configure-antivirus-exclusions-for.html
http://support.microsoft.com/kb/961804
http://support.microsoft.com/kb/822158
On any Hyper-V host you will find a couple of core processes that is crucial to host and VM performance. Prevent the following processes from AV scans by excluding the following as part of you Hyper-V AV policy.
VMMS.exe
VMWP.exe
You also want to exclude the root directories where VM configurations and Virtual Hard Disks are stored. Exclude the following directories.
C:\ProgramData\Microsoft\Windows\Hyper-V
C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
Custom VM configuration, Virtual Hard Disk and Snapshot directories
Next, you want to create AV exclusions for the following file extensions.
*.XML
*.VHD
*.AVHD
*.VFD
*.VSV
*.ISO
Finally, if you are using Hyper-V R2’s Live Migration feature with Cluster Shared Volumes, then you will need to exclude the CSV path and any sub-directories. The CSV path is as follows.
C:\Clusterstorage
Failure to create this exclusion on hosts using CSV, can not only result in poor performance, but can also result in a missing or corrupt VM configuration
Read also the following links:
http://myitforum.com/cs2/blogs/scassells/archive/2007/05/14/what-anti-virus-scanning-exclusions-should-be-considered-for-system-and-servers.aspx
http://www.hypervizor.net/2010/03/configure-antivirus-exclusions-for.html
http://support.microsoft.com/kb/961804
http://support.microsoft.com/kb/822158
On any Hyper-V host you will find a couple of core processes that is crucial to host and VM performance. Prevent the following processes from AV scans by excluding the following as part of you Hyper-V AV policy.
VMMS.exe
VMWP.exe
You also want to exclude the root directories where VM configurations and Virtual Hard Disks are stored. Exclude the following directories.
C:\ProgramData\Microsoft\Windows\Hyper-V
C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
Custom VM configuration, Virtual Hard Disk and Snapshot directories
Next, you want to create AV exclusions for the following file extensions.
*.XML
*.VHD
*.AVHD
*.VFD
*.VSV
*.ISO
Finally, if you are using Hyper-V R2’s Live Migration feature with Cluster Shared Volumes, then you will need to exclude the CSV path and any sub-directories. The CSV path is as follows.
C:\Clusterstorage
Failure to create this exclusion on hosts using CSV, can not only result in poor performance, but can also result in a missing or corrupt VM configuration
Wednesday, April 14, 2010
How to use the "netsh advfirewall firewall"
Read the following article from Microsoft:
http://support.microsoft.com/kb/947709
http://support.microsoft.com/kb/947709
Thursday, March 4, 2010
Microsoft Deployment useful links
Take a look at these links:
http://www.cluberti.com/blog/2009/08/10/mdt-2010-and-deployment-from-a-usb-key/comment-page-1/#comment-591
http://www.svrops.com/svrops/articles/sysprepvista.htm
http://blogs.ethz.ch/jlaville/2008/03/21/step-by-step-vista-and-windows-2008-deployment-with-wds-waik-and-mdt/
http://blog.augustoalvarez.com.ar/2008/12/12/installing-and-configuring-wds-windows-deployment-services-full-images-deployment-part-i/
http://sharepointgeorge.com/2009/windows-deployment-services-waik-and-windows-7-part1/
http://social.technet.microsoft.com/Forums/en-US/mdt/threads
http://www.minasi.com/newsletters/nws1003.htm
http://www.cluberti.com/blog/2009/08/10/mdt-2010-and-deployment-from-a-usb-key/comment-page-1/#comment-591
http://www.svrops.com/svrops/articles/sysprepvista.htm
http://blogs.ethz.ch/jlaville/2008/03/21/step-by-step-vista-and-windows-2008-deployment-with-wds-waik-and-mdt/
http://blog.augustoalvarez.com.ar/2008/12/12/installing-and-configuring-wds-windows-deployment-services-full-images-deployment-part-i/
http://sharepointgeorge.com/2009/windows-deployment-services-waik-and-windows-7-part1/
http://social.technet.microsoft.com/Forums/en-US/mdt/threads
http://www.minasi.com/newsletters/nws1003.htm
Friday, February 19, 2010
Tuesday, February 9, 2010
How to Unregister and Register Virtual Machines without Deleting Them
Read the following articles: http://blogs.msdn.com/robertvi/archive/2008/12/19/howto-manually-add-a-vm-configuration-to-hyper-v.aspx and http://msmvps.com/blogs/virtualreality/archive/2009/03/26/how-to-manipulate-hyper-v-vm-symbolic-links-or-how-to-unregister-and-register-virtual-machines-without-deleting-them.aspx
Thursday, February 4, 2010
Tuesday, November 10, 2009
Your credentials do not work in Hyper-V manager
When you try to connect to a Hyper-V server in Workgroup mode from a client that belongs in either a workgroup or a domain you receive the message:
Your system administrator does not allow the use of default credentials to log on to the remote computer (computer name) because its identity is not fully verified. Please enter new credentials.
The fix is to allow saved credentials with NTLM-only server authentication on the Hyper-V client machine. You can do this in the Local Group Policy Editor.
* Run gpedit.msc on the client machine (Windows Vista or Windows 7)
* Expand Local Computer Policy > Computer Configuration > Administrative Templates > System > Credentials Delegation
* Double-click Allow Saved Credentials with NTLM-only Server Authentication
* Enable the policy
* Add servers to the list by clicking the Show button and adding your Hyper-V hostname like this: */YourServerName
* Add other servers to the list using the same method
* Click OK twice and close Local Group Policy Editor
* Now run GPUPDATE on the Hyper-V client machine to apply the new settings.
* Use cmdkey to save the credentials you use to connect to the remote server using this command: cmdkey /add:ServerName /user:UserName /pass:password
Your system administrator does not allow the use of default credentials to log on to the remote computer (computer name) because its identity is not fully verified. Please enter new credentials.
The fix is to allow saved credentials with NTLM-only server authentication on the Hyper-V client machine. You can do this in the Local Group Policy Editor.
* Run gpedit.msc on the client machine (Windows Vista or Windows 7)
* Expand Local Computer Policy > Computer Configuration > Administrative Templates > System > Credentials Delegation
* Double-click Allow Saved Credentials with NTLM-only Server Authentication
* Enable the policy
* Add servers to the list by clicking the Show button and adding your Hyper-V hostname like this: */YourServerName
* Add other servers to the list using the same method
* Click OK twice and close Local Group Policy Editor
* Now run GPUPDATE on the Hyper-V client machine to apply the new settings.
* Use cmdkey to save the credentials you use to connect to the remote server using this command: cmdkey /add:ServerName /user:UserName /pass:password
Subscribe to:
Posts (Atom)