Tag Archives: Windows

Linux SSH + PAM + LDAP + SSSD+ 2008 R2 AD Deployment

As an update to my previous post “Linux SSH + PAM + LDAP + 2003 R2 AD Deployment“, SSSD is now part of the base RHEL6 repository (soon CentOS6 as well) which makes it much faster and easier to implement LDAP/AD authentication.  In regards to configuring Active Directory, not too much has changed since my previous post so you’ll need to hit up the previous guide for a complete guide.  So lets get to it..

Continue reading

Remote Server Shutdown

One of my recent projects was to initiate a server-wide shutdown should our UPS ever run low.  I currently have Zenoss monitoring the health status of the UPS, including the remaining charge on the battery.  Using Zenoss thresholds, I can make a script execute if the battery ever runs low.

Our Zenoss deployment currently runs on CentOS, so I put down a method to shut down each type of host from a linux platform.  After much researching and testing, this is what I came up with (and am currently using in my shutdown script).

For Windows:

net rpc SHUTDOWN -C "Automated shutdown" -f -I "$server" -W $domain -U $username%$password

I replaced my arguments with some that would be more readable.  User and password are separated with %.

For Linux:

CMD="ssh -l $username $server shutdown -h now"
              expect -c "
              match_max 100000
              spawn $CMD
              expect {
                \"Are you sure you want to continue connecting (yes/no)?\" {
                send \"yes\r\"
                \"password:\" {
                send \"$password\r\"
                expect -re \"$username*\"

I wanted to shutdown linux servers without using keys but had to overcome the “do you want to connect” prompt.  In order to do that I had to use exact which can be installed with “yum install exact”

By turning these into functions and passing arguments, you can make a shutdown script in a couple of minutes.

VMware – Windows AMD PCNet Family Adapater Issue

Since we have ESX, I usually don’t get to spend much time playing around with VMware-Server. Interested to see the new interface in VMware-Server 2, I installed it on one of my CentOS servers.dm

The installation was a breeze with the rpm package and running the configuration script was pretty flawless. So I logged in through the Remote Management Console (https/port 8333), and created a fresh host. After copying over a Win2k3 iso, mounted the image and began the installation.

(On a side note I was doing this remotely, and found out that in order to use the Remote Console Client, I needed to allow ports 8333 and 902 through the firewall)

The initial Windows installation zipped right through, however, when I went to configure the network adapter none was listed. So I took a look at the Device Manager and BAM!
This device cannot start. (Code 10)

Having never come across this on VMware/Windows installation, I decided to reinstall my Windows host. Same thing.. So let’s install the driver.. that we need to download.. with no network card..

Lucky for us we have VMware! Downloaded the latest PCNet Family drivers for Windows 2003, tossed them in an .iso image, and mounted it to the Virtual CD-Rom for the host. Once I extracted/updated the driver, everything was running smooth again.

Download the .iso image here: AMD Driver v4
MD5: 78159679b644e64c0ca5618bc4de1995

Auto Logon with Windows XP

Sometimes I need to remind myself where this is located.  This is primarily useful when you have shared domain workstations that need to logon automatically.  Be sure to lock this workstation down!

KB #315231

This article describes how to configure Microsoft Windows XP to automate the logon process by storing your password and other pertinent information in the registry database. This feature permits other users to start your computer and to use the account that you establish to automatically log on.

Important If you turn on autologon, using Windows XP becomes more convenient. However, using this feature can pose a security risk.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

Continue reading

WDS Image Creation

As a continuation of my previous WDS post located here, these are the steps I follow for creating my WDS images.

  • Install OS, drivers, service packs, software, updates, and everything else to master system.
  • Copy Windows installation media to local drive: xcopy /H /E D:\* C:\windows\options\cabs\
  • Copy deploy.cab from recent installation media, extract to sysprep folder located on the administrator’s desktop.
  • From a Windows command prompt, browse to sysprep folder and run:  sysprep.exe -mini -reseal (with optional flags) 
  • Wait for system to shutdown..  start system back up, ensure PXE or network boot is enabled.
  • Boot from PXE/WDS, select Windows PE from options menu. 
  • At Windows PE command prompt, run: wdscapture
  • Follow Windows Image Capture wizard.

RDPDD.dll Failed to Load

After installing .NET 3.0 on one of my test servers, I could no longer connect over RDP.  From the client, the connection would just terminate with no errors.  After looking at the Windows Event Log on the server, I found:

Event ID: 26
Application popup:  : \SystemRoot\System32\RDPDD.dll failed to load

After looking around, this appears to be an issue with the installed nVidia driver, though ATI users have experienced this as well.  Adding the following registry value and rebooting, I was able to RDP again.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

Windows Server 2003 (32bit) – Max Event Log Size

Just going to make this short and simple, there are many places, including Microsoft documentation, which state you can set the event log size up to 4GB.  While this is true, it will never get remotely close to reaching that size, or 1GB even.  Due to some very bad design, the event log uses memory mapped files under the services.exe process, which due to another very bad design, is limited to 1GB pool.


This apparently is not an issue in 2003 64bit, and is resolved in 2008.