How to move WSUS UpdateServicesDbFiles folder and susdb.mdf
By default, WSUS 3.0 on SBS 2003 R2 server uses Windows Internal Database.
If WSUS 3.0 uses other versions of SQL server, the moving steps will be a little different, but the procedures are almost same. They are:
1. Detach SUSDB from SQL Server.
2. Move SUSDB.mdf and SUSDB_Log.ldf to the new location.
3. Attach SUSDB to SQL Server again.
If WSUS 3.0 is using Windows Internal Database, please follow these steps to move SUSDB:
1. Open a "CMD" command window, and run these commands to stop the WSUS service and IIS:
net stop wsusservice
iisreset /stop
2. Detach the SUSDB.
a. Follow the instructions to download and install "Microsoft SQL Server Management Studio Express" on the WSUS server:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6053c6f8-82c8-479c-b25b-9aca13141c9e
(Please note: we need to install MSXML6 and .Net Framework 2.0 first. If this tool already exists, please ignore this step.)
b. Click "Start"->"All Programs"->"Microsoft SQL Server 2005"->"SQL Server Management Studio" to run this tool.
c. Select the SQL server/instance used by WSUS, and then click Connect. For WSUS 3.0 with Windows Internal Database, please copy/paste this name:
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
(If this name is unreachable, please WSUS may not use Windows Internal Database, please verify this registry value to confirm the SQL name:
HKEY_LOCAL_MACHINE\Software\Microsoft\Update Services\Server\Setup\SqlServerName.%computername%\MICROSOFT##SSEE means Windows Internal Database.)
d. Expand the "Databases" node from the left pane; Right click the "SUSDB", then click "Tasks"->"Detach" and "OK".
If it fails, please select the "Drop Connections" checkbox and try again.
3. Move the SUSDB.mdf and SUSDB_Log.ldf to a new location by Windows Explorer. By default, they are in the "<Driver>:\WSUS\UpdateServicesDbFiles" folder.
4. Attach the SUSDB database from the new location.
a. Switch back to the Management Studio and right click the "Databases" node, and then click "Attach".
b. Click "Add" button; Navigate to the new location, and then select the SUSDB.mdf and click "OK".
5. Start the WSUS and IIS services with these commands:
net start wsusservice
iisreset /start
Programs I can’t live without!
I have had plenty of people ask me what I run on my computer and what programs they should run. Well It's hard to tell someone what programs they should run as I do not know what you use your computer for. But I can tell you what programs I run and cant live without. Last night I built a new computer as I have been running the same computer for about 5 years now. It was definitely time to upgrade. So here is the list of programs I installed as soon as I finished installing Windows. You will note that all of the programs listed below are free and available to download.
- Firefox (A web browser that I prefer over Internet Explorer for its extensions)
- Xmarks (Extension for Firefox (allows me to sync my bookmarks between my computers)
- Web Developer (A Firefox extension that adds a web developer toolbar with all sorts of useful things)
- Toggle Web Developer Toolbar (adds an icon to toggle the Web Developer Toolbar)
- Google Chrome (Yes I run more then one web browser. I basically just use chrome to view my business email.)
- Adobe Flash Player (Almost every website today requires adobe flash to play animated adds or watching movies.)
- Foxit Reader (A lightweight Acrobat file reader that I prefer over Adobe Acrobat Reader)
- Dropbox (Dropbox is a file sync tool to sync files between multiple computers. Great tool if you have a desktop and a laptop and want to have some files available on both.)
- Notepad++ (Can't live without this text editor. It's an advanced version of notepad with line numbers and highlights multiple types of code for those that prefer to edit code with a txt editor.)
- FileZilla Client (An open source FTP file transfer application. I use this for uploading website files.)
- OpenOffice (An open source office suite that is comparable to Microsoft Office)
- MagicISO Virtual CD/DVD-ROM (A virtual CD/DVD-Rom software allowing you to mount ISO images and have them show up as if you have multiple DVD drives.)
- uTorrent (A torrent downloading application for downloading Torrents.)
- WINAMP (A great media player that I have been using since middle school.)
- TeamViewer (A remote access application that you can use to remotely access your computer or give remote support to others. Free for personal use.)
- doPDF (A PDF print distiller for creating PDF files from any program by printing to doPDF.)
- KeePass (A password manager application for storing passwords)
- KeeFox (A Firefox plugin to integrate KeePass into Firefox)
- VLC Media Player (A free open source multimedia player.)
- Microsoft Security Essentials (a free Anti-Virus program that Microsoft released a few years ago.)
- 7-Zip (Open Source file compression software)
- Backup Planet (Online Backup software so I know I will never loose any data)
Find more great open soure applications to fit your needs at GetLEET.com GeetLEET.com is a website I created to post open source applications that I use from time to time. Mainly a place so I can actually remember what I have used and find where to download it again.
Determining and transfer FSMO roles to a new Domain Controller
The following list describes the 5 unique FSMO roles in an Active Directory forest and the dependent operations that they perform:
- Schema master - The Schema master role is forest-wide and there is one for each forest. This role is required to extend the schema of an Active Directory forest or to run the adprep /domainprep command.
- Domain naming master - The Domain naming master role is forest-wide and there is one for each forest. This role is required to add or remove domains or application partitions to or from a forest.
- RID master - The RID master role is domain-wide and there is one for each domain. This role is required to allocate the RID pool so that new or existing domain controllers can create user accounts, computer accounts or security groups.
- PDC emulator - The PDC emulator role is domain-wide and there is one for each domain. This role is required for the domain controller that sends database updates to Windows NT backup domain controllers. The domain controller that owns this role is also targeted by certain administration tools and updates to user account and computer account passwords.
- Infrastructure master - The Infrastructure master role is domain-wide and there is one for each domain. This role is required for domain controllers to run the adprep /forestprep command successfully and to update SID attributes and distinguished name attributes for objects that are referenced across domains.
Display the Current FSMO Role Holders
Before transfering your FSMO roles to a new server you may want to know what current Domain Controller holds each FSMO role. There is a really easy way to do this from the command prompt. You can open Active Directory Users and Computers and view the Operating Masters but this only shows you a few. The command prompt is the fastest easiest way.
- Open Command Prompt
- Type netdom query fsmo

- The output above will give you a current list of all FSMO role holders
Transfer FSMO Role Holders
Microsoft recommends that you transfer FSMO roles in the following scenarios:
- The current role holder is operational and can be accessed on the network by the new FSMO owner.
- You are gracefully demoting a domain controller that currently owns FSMO roles that you want to assign to a specific domain controller in your Active Directory forest.
- The domain controller that currently owns FSMO roles is being taken offline for scheduled maintenance and you need specific FSMO roles to be assigned to a “live” domain controller. This may be required to perform operations that connect to the FSMO owner. This would be especially true for the PDC Emulator role but less true for the RID master role, the Domain naming master role and the Schema master roles.
To migrate from one Domain Controller to another you will need to transfer the FSMO roles after running DCPROMO on the new domain controller. The easiest way to do so is by the command prompt.
- Open Command Prompt
- Type ntdsutil, and then press ENTER
- Type roles, and then press ENTER.
- Type connections, and then press ENTER.
- Type connect to server servername, and then press ENTER, where servername is the name of the domain controller you want to assign the FSMO role to.
- At the Server Connections prompt, type q, and then press ENTER.
- Type transfer role, where role is the role you want to transfer. For a list of roles that you can transfer, type ? at the fsmo maintenance prompt, and then press ENTER, or see image below.

- At the fsmo maintenance prompt, type q, and then press ENTER to gain access to the ntdsutil prompt. Type q, and then press ENTER to quit the Ntdsutil utility.
Seise FSMO Role Holders
Microsoft recommends that you seize FSMO roles in the following scenarios:
- The current role holder is experiencing an operational error that prevents an FSMO-dependent operation from completing successfully and that role cannot be transferred.
- A domain controller that owns an FSMO role is force-demoted by using the dcpromo /forceremoval command.
- The operating system on the computer that originally owned a specific role no longer exists or has been reinstalled.
The seise command is great when your current role holder is no longer on the domain. I have seen multiple companies where the current role holder was inproperly decomisioned and still holds FSMO roles but the physical server is long gone. This is the main reason I have had to seise FSMO roles. A domain controller whose FSMO roles have been seized should not be permitted to communicate with the existing domain controllers in the forest. If you have to seise the FSMO roles from a domain controller either format that servers hard drive or reinstall windows to be sure that domain controller is never reintroduced to the forest.
- Open Command Prompt
- Type ntdsutil, and then press ENTER
- Type roles, and then press ENTER.
- Type connections, and then press ENTER.
- Type connect to server servername, and then press ENTER, where servername is the name of the domain controller you want to assign the FSMO role to.
- At the Server Connections prompt, type q, and then press ENTER.
- Type seize role, where role is the role you want to transfer. For a list of roles that you can transfer, type ? at the fsmo maintenance prompt, and then press ENTER, or see image below.

- At the fsmo maintenance prompt, type q, and then press ENTER to gain access to the ntdsutil prompt. Type q, and then press ENTER to quit the Ntdsutil utility.
Multi Day SharePoint Services 3 batch file backup w/email reporting
I created a batch script to backup SharePoint Services 3 and email a backup report to my email address. I know there is VBScripts out there that do the same thing but I wanted to create a batch file that backs up SharePoint with retention and email reporting as it would be easier for others to modify that don't know VB.
Key Features
- Backs up SharePoint to c:\spbackups
- Copies the backup files to a remote server
- Keeps a 7 days retention of SharePoint backups
- Emails you a backup report stating the backup has completed successfully
- Lists all backup files in the backup folder and on the remote server within the backup report email
- Lists all files on the remote server
- Uses MAILSEND to email you a backup report
Here is the script
echo SharePoint Services 3 - 7 Day Command Line Backup Script echo Created by: Mike Brawley echo Website: http://www.mikebrawley.com REM ########################################################################## REM REM This script will backup Microsoft SharePoint with 7 days of retention REM Before the backup begins it renames your old backups to archive them REM After the backup has finished it will copy the backup to a remote server REM When the backup is finished it will email you a log with the directory list REM of both the local and remote versions of the backup files REM REM ########################################################################## REM REM Configure all parameters set below REM REM ########################################################################## set location=c:\spbackups set remotelocation=\\server\share\folder set relayserver=smtp.server.com set yoursite=https://sharepoint.yourcompany.com set templog=c:\spbackups\spbackuplog.txt set file=SPBackup.bak set emailsub=SharePointBackupReport set domain=yourcompany.com set to=you@yourcompany.com set reply=noreply@yourcompany.com set STSADM=C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\Stsadm.exe REM ########################################################################## REM REM Do not edit below this point REM REM ########################################################################## del %location%\%file%.7day rename %location%\%file%.6day %file%.7day rename %location%\%file%.5day %file%.6day rename %location%\%file%.4day %file%.5day rename %location%\%file%.3day %file%.4day rename %location%\%file%.2day %file%.3day rename %location%\%file%.1day %file%.2day rename %location%\%file% %file%.1day "%STSADM%" -o backup -overwrite -url %yoursite% -backupmethod full -filename %location%\%file% > %templog% del %remotelocation%\%file%.7day rename %remotelocation%\%file%.6day %file%.7day rename %remotelocation%\%file%.5day %file%.6day rename %remotelocation%\%file%.4day %file%.5day rename %remotelocation%\%file%.3day %file%.4day rename %remotelocation%\%file%.2day %file%.3day rename %remotelocation%\%file%.1day %file%.2day rename %remotelocation%\%file% %file%.1day XCOPY %location%\%file% %remotelocation% dir %location% >> %templog% dir %remotelocation% >> %templog% MAILSEND -d "%domain%" -smtp "%relayserver%" -t "%to%" -f "%reply%" +cc +bc -sub "%emailsub%" -m "%templog%,text/plain" -a "%templog%,text/plain"
Instructions
- Download the Backup Script Files
- Extract its contents to c:\ on your SharePoint server
- Navigate to C:\SPTools\ and open SPBackup.bat in a text editor. (I recommend Notepad++)
- Set all parameters within SPBackup.bat for your specific SharePoint
- Create a task in Task Scheduler to run this script daily.
- If you would like to push your SharePoint backup offsite you can add C:\SPBackup to your online backup selection list. (I recommend Backup Planet for online backup)
Please feel free to modify and distribute this script in anyway you like.
Beyond Windows 7 God Mode
Many of you enjoyed the God Mode "trick" so here's a few more released by Microsoft. If you do not know what God mode is I have listed it below as well for you to try out.
1. Open Windows Explorer and create a new folder
NOTE: Creating the folder on the Desktop might or might not work. I have had mixed experiences when creating this on the desktop.
2. Rename the folder by pasting the name below exactly as it appears:
GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}
(note that you can change the “GodMode” text, but the following period and code number are essential).
And some others.
Microsoft.ActionCenter.{BB64F8A7-BEE7-4E1A-AB8D-7D8273F7FDB6}
Microsoft.AdministrativeTools.{D20EA4E1-3957-11d2-A40B-0C5020524153}
Microsoft.AutoPlay.{9C60DE1E-E5FC-40f4-A487-460851A8D915}
Microsoft.BackupAndRestore.{B98A2BEA-7D42-4558-8BD1-832F41BAC6FD}
Microsoft.BiometricDevices .{0142e4d0-fb7a-11dc-ba4a-000ffe7ab428}
Microsoft.BitLockerDriveEncryption.{D9EF8727-CAC2-4e60-809E-86F80A666C91}
Microsoft.ColorManagement.{B2C761C6-29BC-4f19-9251-E6195265BAF1}
Microsoft.CredentialManager.{1206F5F1-0569-412C-8FEC-3204630DFB70}
Microsoft.DateAndTime.{E2E7934B-DCE5-43C4-9576-7FE4F75E7480}
Microsoft.DefaultLocation.{00C6D95F-329C-409a-81D7-C46C66EA7F33}
Microsoft.DefaultPrograms.{17cd9488-1228-4b2f-88ce-4298e93e0966}
Microsoft.DesktopGadgets .{37efd44d-ef8d-41b1-940d-96973a50e9e0}
Microsoft.DeviceManager.{74246bfc-4c96-11d0-abef-0020af6b0b7a}
Microsoft.DevicesAndPrinters .{A8A91A66-3A7D-4424-8D24-04E180695C7A}
Microsoft.Display.{C555438B-3C23-4769-A71F-B6D3D9B6053A}
Microsoft.EaseOfAccessCenter.{D555645E-D4F8-4c29-A827-D93C859C4F2A}
Microsoft.FolderOptions.{6DFD7C5C-2451-11d3-A299-00C04F8EF6AF}
Microsoft.Fonts.{93412589-74D4-4E4E-AD0E-E0CB621440FD}
Microsoft.GameControllers.{259EF4B1-E6C9-4176-B574-481532C9BCE8}
Microsoft.GetPrograms.{15eae92e-f17a-4431-9f28-805e482dafd4}
Microsoft.GettingStarted.{CB1B7F8C-C50A-4176-B604-9E24DEE8D4D1}
Microsoft.HomeGroup.{67CA7650-96E6-4FDD-BB43-A8E774F73A57}
Microsoft.IndexingOptions.{87D66A43-7B11-4A28-9811-C86EE395ACF7}
Microsoft.Infrared.{A0275511-0E86-4ECA-97C2-ECD8F1221D08}
Microsoft.InternetOptions.{A3DD4F92-658A-410F-84FD-6FBBBEF2FFFE}
Microsoft.iSCSIInitiator.{A304259D-52B8-4526-8B1A-A1D6CECC8243}
Microsoft.Keyboard.{725BE8F7-668E-4C7B-8F90-46BDB0936430}
Microsoft.LocationAndOtherSensors.{E9950154-C418-419e-A90A-20C5287AE24B}
Microsoft.Mouse.{6C8EEC18-8D75-41B2-A177-8831D59D2D50}
Microsoft.NetworkAndSharingCenter.{8E908FC9-BECC-40f6-915B-F4CA0E70D03D}
Microsoft.NotificationAreaIcons.{05d7b0f4-2121-4eff-bf6b-ed3f69b894d9}
Microsoft.OfflineFiles.{D24F75AA-4F2B-4D07-A3C4-469B3D9030C4}
Microsoft.ParentalControls.{96AE8D84-A250-4520-95A5-A47A7E3C548B}
Microsoft.PenAndTouch.{F82DF8F7-8B9F-442E-A48C-818EA735FF9B}
Microsoft.PeopleNearMe.{5224F545-A443-4859-BA23-7B5A95BDC8EF}
Microsoft.PerformanceInformationAndTools.{78F3955E-3B90-4184-BD14-5397C15F1EFC}
Microsoft.Personalization.{ED834ED6-4B5A-4bfe-8F11-A626DCB6A921}
Microsoft.PhoneAndModem.{40419485-C444-4567-851A-2DD7BFA1684D}
Microsoft.PowerOptions.{025A5937-A6BE-4686-A844-36FE4BEC8B6D}
Microsoft.ProgramsAndFeatures.{7b81be6a-ce2b-4676-a29e-eb907a5126c5}
Microsoft.Recovery.{9FE63AFD-59CF-4419-9775-ABCC3849F861}
Microsoft.RegionAndLanguage.{62D8ED13-C9D0-4CE8-A914-47DD628FB1B0}
Microsoft.RemoteAppAndDesktopConnections.{241D7C96-F8BF-4F85-B01F-E2B043341A4B}
Microsoft.ScannersAndCameras.{00f2886f-cd64-4fc9-8ec5-30ef6cdbe8c3}
Microsoft.Sound.{F2DDFC82-8F12-4CDD-B7DC-D4FE1425AA4D}
Microsoft.SpeechRecognition.{58E3C745-D971-4081-9034-86E34B30836A}
Microsoft.SyncCenter.{9C73F5E5-7AE7-4E32-A8E8-8D23B85255BF}
Microsoft.System.{BB06C0E4-D293-4f75-8A90-CB05B6477EEE}
Microsoft.TabletPCSettings.{80F3F1D5-FECA-45F3-BC32-752C152E456E}
Microsoft.TaskbarAndStartMenu.{0DF44EAA-FF21-4412-828E-260A8728E7F1}
Microsoft.TextToSpeech.{D17D1D6D-CC3F-4815-8FE3-607E7D5D10B3}
Microsoft.Troubleshooting.{C58C4893-3BE0-4B45-ABB5-A63E4B8C8651}
Microsoft.UserAccounts.{60632754-c523-4b62-b45c-4172da012619}
Microsoft.WindowsAnytimeUpgrade.{BE122A0E-4503-11DA-8BDE-F66BAD1E3F3A}
Microsoft.CardSpace.{78CB147A-98EA-4AA6-B0DF-C8681F69341C}
Microsoft.WindowsDefender.{D8559EB9-20C0-410E-BEDA-7ED416AECC2A}
Microsoft.WindowsFirewall.{4026492F-2F69-46B8-B9BF-5654FC07E423}
Microsoft.MobilityCenter.{5ea4f148-308c-46d7-98a9-49041b1dd468}
Microsoft.WindowsSideShow.{E95A4861-D57A-4be1-AD0F-35267E261739}
Microsoft.WindowsUpdate.{36eef7db-88ad-4e81-ad49-0e313f0c35f8}
Microsoft.NetworkFolder.{208D2C60-3AEA-1069-A2D7-08002B30309D}
3. Windows Vista-specific codes
Microsoft.AddHardware.{7A979262-40CE-46ff-AEEE-7884AC3B6136}
Microsoft.AudioDevicesAndSoundThemes.{F2DDFC82-8F12-4CDD-B7DC-D4FE1425AA4D}
Microsoft.BackupAndRestoreCenter.{B98A2BEA-7D42-4558-8BD1-832F41BAC6FD}
Microsoft.InfraredOptions.{A0275511-0E86-4ECA-97C2-ECD8F1221D08}
Microsoft.PenAndInputDevices.{F82DF8F7-8B9F-442E-A48C-818EA735FF9B}
Microsoft.PhoneAndModemOptions.{40419485-C444-4567-851A-2DD7BFA1684D}
Microsoft.Printers.{2227A280-3AEA-1069-A2DE-08002B30309D}
Microsoft.ProblemReportsAndSolutions.{FCFEECAE-EE1B-4849-AE50-685DCF7717EC}
Microsoft.RegionalAndLanguageOptions.{62D8ED13-C9D0-4CE8-A914-47DD628FB1B0}
Microsoft.SecurityCenter.{087DA31B-0DD3-4537-8E23-64A18591F88B}
Microsoft.SpeechRecognitionOptions.{58E3C745-D971-4081-9034-86E34B30836A}
Microsoft.WelcomeCenter.{CB1B7F8C-C50A-4176-B604-9E24DEE8D4D1}
Microsoft.WindowsSidebarProperties.{37efd44d-ef8d-41b1-940d-96973a50e9e0}
4. Name your folder
Once you edit the folder and enter one of the lines above, the folder will change to be one of the God Mode elements. Once this has been performed you can then rename the folder again to whatever you want.
5. Warning
The trick works on both the 32 and 64-bit versions of Windows 7. Vista 32-bit and Windows Server 2008 32-bit should also work. However, it is known to crash 64-bit versions of Vista — and you may need to boot in safe mode or to the command line to delete the folder. I do not recommend performing any of the following on a production server!
Hyper-V hard drive full, avhd and vhd files?
The AVHD files are differencing disks which work in conjunction with the parent VHD file. At the point the snapshot of the VM was created, the parent VHD essentially became read-only and all the changes or additions to disk made by the VM were actually being written to the AVHD file. This allows snapshots to do their job by giving the flexibility to dump all those changes and return the VM to its original state at the top of the snapshot tree.
I had 3 AVHD files that I wanted to get rid of, so I turned the VM Off in question and the “Merge in Progress” appeared in the Hyper-V Manager so I let it run it’s course. About 50 mins later the merge process was complete and 2 of the AVHD Files where removed, great! but there was still one left? So I decided to turn the VM off again and what do you know another Merger was taking place, so again I left this happen and after it had completed the final AVHD File disappeared and I was left with one VHD File, FANTASTIC!
One thing I learned from this experience was that the VM writes to the AVHD Files and doesn’t appear to touch the VHD File (Parent File). I think I got myself into this situation because the Snap Shots were not deleted corectly. It seams that Hyper-V is different in the way it deals with snapshots over xenserver or vmware.
VMWare and Xenserver both automatically merge its snapshot files into its parent file once you delete the snapshot from the snapshot manager. With Hyper-V it seams as if you must shutdown the server the snapshot was deleted from for a period of time while the files merge. This definitely changes how ofter or for what reason you would want to take snapshots of your server.
Do keep in mind you never want to run a server for long periods of time with snapshots. When running a server with snapshots you are reading files from within multiple virtual hard drive files. This degrades server performance significantly. With Hyper-V if your parent VHD file is 200GB to start with and you take a snapshot. That snapshot file will grow constantly every time a file needs to be written to. Running Hyper-V servers with snapshots you run into the probability of running out of hard drive space on your host server as the snapshot AVHD file constantly grows in size till you delete the snapshot and shutdown the server to allow the files to merge.
I found a good 2 part article about reclaiming lost hard drive space on Hyper-V on Virtualadmin.com




