How to Manage Local Password Policy on Windows Server 2008 Core

How to Manage Local Password Policy on Windows Server 2008 Core

Video Tutorials, Windows Server
Windows Server 2008 Core is a minimal server installation option for computers running on the Windows Server 2008 operating system. Server Core provides a low-maintenance server environment with limited functionality. Windows Server 2008 Core supports the following server roles: Active Directory Domain Services (AD DS) Active Directory Lightweight Directory Services (AD LDS) DHCP Server DNS Server File Services Print Services Streaming Media Services Internet Information Services (IIS) Virtualization Local Security Policy allows enforcing many system, user and security-related settings, such as password policy, audit policy and user rights. Event Viewer can then be used to check log events.
Read More

How to Install Service Pack in Windows Server Failover Cluster for Windows 2008 R2, Windows 2008 and Windows 2003

Windows Server
The process of applying a service pack to a server failover cluster is almost the same as applying it to Windows 2008 R2, Windows 2008 and Windows 2003. You can install Windows service packs on Windows Server Failover Cluster nodes using the following procedure. Always install the same service packs or hotfixes to each node. Use this procedure to install the service packs unless otherwise directed by a particular service pack version. Open Failover Cluster Manager, and then click Nodes then right-click Node A, and then click Pause. Expand Node A. In the right pane, right-click each Services or applications and then click Move this service or application to another node to move them to Node B. Install the service pack on Node A, and then restart the Node A. In Failover Cluster Manager, right-click Node A,…
Read More
Error 0x80092013: The revocation function was unable to check revocation because the revocation server was offline

Error 0x80092013: The revocation function was unable to check revocation because the revocation server was offline

Windows Server
Problem: You followed all steps from a Deploying SSTP Remote Access Step by Step Guide. However, when vista or windows 7 client tries to connect VPN server you get this error: " The revocation function was unable to check revocation because the revocation server was offline. " Workaround: The SSL VPN client needs to be able to download the CRL to confirm that the server certificate on the VPN server has not been revoked. You must either publish the CRL on a server that is accessible on the Internet or configure the client to not require CRL checking.. Because it exposes a private server name to the Internet, you can do the following as an alternative solution. Solution: Disable CRL Checking on VPN Client To disable CRL checking, create a…
Read More

Windows Server 2008 R2 Best Practices in VMware vSphere 4.X

VMware, Windows Server
Be sure the virtual machine has at least 2GB of RAM. Hard drive for the virtual machine must be 20GB or larger. Single VCPU works better for Windows 2008, Because Windows 2008 uses high bit rate address space for context switching when compared with Windows 2003, which creates multiple cycles of high bit range contexts and these are better addressed by Single VCPU. (this again vary if it is a DB server). VCPU will get hit, when VMware have wide variety of hardware components attached to VM (Majorly Serial and Parallel COM ports, USB controllers, Sound Cards etc), if any of these components are not required, remove them and disable them from VM BIOS. Zeroed Thick: Space required for the virtual disk is allocated at creation time, hoVMwarever the data…
Read More

KB373931- Srv2.sys SMB 2.0 Server Driver Fix – Windows Server 2008 R2 BSoD Problem – Windows6.1-KB373931-x64

Windows Server
Some Windows 2008 R2 servers may experience BlueScreen and Reboot problem. If these servers are using File Share or SMB v.2, srv2.sys may cause this problem. There is problem related to Srv2.sys driver. This is SMB 2.0 server driver. You can install this hotfix KB373931 for Windows Server 2008 R2 SP1 with your own risk.  
Read More
WinRM service failed to create the following SPNs: WSMAN – Event ID:10154

WinRM service failed to create the following SPNs: WSMAN – Event ID:10154

Linux, Windows Server
I was getting an error " The WinRM service failed to create the following SPNs: WSMAN/hostname; WSMAN/hostname. " at startup on Windows 2008 R2 Domain Controllers. Additional Data Log Name: System Source:  Microsoft-Windows-WinRM Event ID: 10154 Level:  Warning Solution: WinRM runs under " Network Service " account. You can eliminate this problem by giving Validated Write to Service Principal Name  permission to the NETWORK SERVICE using the ADSIEDIT.msc. This will allow WinRM to auto create the necessary SPNs on that domain controller. After granting this permission, re-sync all DCs and do a reboot to each domain controller where you did the change,  after that reboot you will see that the warning is gone and the required SPNs were created successfully. Steps: 1- Use ADSIEDIT.msc 2- Choose Default naming context and…
Read More