The VSS simply lacks a required windows update, which is KB940349.
The VSS has a memory leak and needs to be patched with KB870973.

My problem was resolved after installing KB940349.

or through updating Samba to the newest version using online update.

The solution for this is to run a command to get the adapter id list, then to edit the registry.  Run the following in an elevated command prompt: wmic nicconfig get Description,SettingID
There should be two columns of output from the command.  The setting ID will give you the information you need to edit the registry.

Open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage
In this path there should be three strings.  The value of each of the strings contains the network device ID’s in the opposite order of their priority [the last (furthest right) ID is the one with the highest priority] change these settings to suite your needs and reboot to put them into effect.

This will tell launchd to stop automatically relaunching the process after you turn it off or kill the pid.

Encountered an issue with configuring SNMP on a Server 2008 core installation today.  I enabled SNMP but could not figure out how to actually configure it.  With Server 2008 Core you can not run the Microsoft Management Console, so no serverices.msc to configure it.  And when connecting to the server remotly through the services management console you do not get the extra tabs on the SMNP service.

The only way I could find around this was to use one of my other full gui Server 2008 installs to configure SMNP and then export the registry key (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP) and import it into the Core installation.

There seems to still be some confusion regarding the activation methods for of Microsoft Windows Vista and Server 2008.  The two methods are Key Management System and Multiple Key Management.  Microsoft recommends KMS for environments with more than 25 computers.

Pros for KMS include the fact that there is no client configuration necessary and the method only requires the client to have access to the KMS host to activate, not necessarily the Internet.  Another plus is that KMS adds a DNS SRV record, this allows new servers to discover and activate automatically.  The downside to using KMS is that the machine must reactivated every 180 days and that a minimum of 5 KMS clients are required to activate KMS.  The main draw to MAK is that you only need to activate once and no additional infrastructure is required to activate.

The only downsides to using MAK are that you must manually activate each host and that once a key has reached its maximum product activation count you will be forced to call Microsoft each time you activate beyond that point.

route add default gw mango-gw

adds a default route (which will be  used  if  no  other  route matches).   All  packets  using  this  route  will be gatewayed through “mango-gw”. The device which will actually be used  for that  route depends on how we can reach “mango-gw” – the static route to “mango-gw” will have to be set up before.

The only two things you need to reset the domain admin password is the local administrator password (which can also easily be reset, but that is another post) and two files that are part of the Microsoft Windows Server 2003 Resource Kit Tools.

First off you should prepare the two files you will need from the resource kit.  Download the resource kit, install the toolkit, and copy the files srvany.exe and instsrv.exe to a folder named “temp” on a thumbdrive or cd.  Then boot the domain controller into directory services restore mode.  This can be done through pressing F8 at bootup the same as if you were entering safe mode.  After this you will need to copy the temp folder that you placed the files srvany.exe and instsrv.exe in to the root of the c:.  After this you will go to run and type CMD and hit enter.  (Note: I will use put command in between dashes – example command – so you know what exactly to type, do not include the dashes when typing.)  Type – cd.. – and hit enter, repeat this until the prompt shows c:\.  Type – cd temp – hit enter, then – instsrv PassRecovery “C:\temp\srvany.exe” -

After receiving the notice that the previous task completed you can close the command prompt.  Go to run and type regedit and hit enter.  Go to HKLM>System>CurrentControlSet>Services>PassRecovery.  Create a new subkey called Parameters.  Do this by right clicking on PassRecovery and selecting new key.  Add two new strings to this new subkey.  The first of which will be called Application and the value will be c:\temp\cmd.exe  The second will be called AppParameters and the value will be – /k net user administrator yourP@ssword1 /domain -  Remember to not include the dashes…  Replace yourP@ssword1 with a password that will be complaint with your domain policy.  The next step will be to copy cmd.exe from C:\windows\system32 to C:\temp.  The final step will be to go to run, type services.msc hit enter.  Look for PassRecovery and go to its properties.  Ensure that the service is set to automatic.

Restart the computer normally and login with your new credentials.  The only step left is to clean up the new service.  Go to run, type cmd, hit enter.  type – net stop PassRecovery – hit enter.  Then type – sc delete PassRecovery – The only thing left is to delete the c:\temp folder that you copied onto the drive.

For those that like to understand what exactly we did I will give a brief explanation.  The instsrv.exe utility installs a service.  The srvany.exe allows you to run an application as a service.  Running srvany.exe as a service  running on startup allows you to execute the” net user” command with the system credentials.