How-to run Win2k3 NTBackup on Windows Server 2008

Copy the following binaries from Windows 2k3 server (C:\Windows\System32\) to Windows Server 2008 (C:\Program Files\NTBackup\):

  • ntbackup.exe
  • ntmsapi.dll
  • vssapi.dll

Then install the removable storage manager from server manager:

  • Start Server Manager
  • Click Features
  • Click Add Features
  • Select Removable Storage Manager
  • Click Install

When NTBackup starts, if you see an error regarding removable storage, just ignore it and click “Do not show this again”.

I’m not sure, but it seems that it backup Exchange 2007 Databases too, for me it worked, but I didn’t tested restoring them.

June 16th, 2009, posted by admin

Fixing Adobe Flash Player on Vista

For you Vista users out there, if you’re seeing strange issues with Adobe Flash, where the plugin is installed but not recognized on certain sites, I have a solution for you. The “installation successful” page tells me that I have Flash installed. I can see the Flash banners just fine. Yet when try to watch a video on a page that uses Flash, it tells me that I need to have the latest Flash player installed. I’ve confirmed that “Shockwave Flash Object” is installed (Tools > Manage Add-Ons), and Flash10a.ocx is the file name. If you’re having the same problem, keep reading.

Even though Adobe’s online tool said I was running the latest version of Flash (10.0.12.36), it still wasn’t working properly. I ran across a forum post that suggested trying several things, so I found the install folder for Flash:

C:\Windows\System32\Macromed\Flash

Inside that folder, there are two files: Flash10a.ocx, the ActiveX control that IE7 uses, and FlashUtil10a.exe. I shut down IE7 then ran FlashUtil10a.exe and it said that there was an update for my version of Flash – downloaded the new version, rebooted the PC as suggested, and now I can view all Flash content as I should. What’s interesting is that the version number of Flash didn’t change. I suspect the issue is more one of registering Flash with the system properly, and Adobe has a bug in the installer. This worked for me, so I hope it will work for you!

March 31st, 2009, posted by Erik Klavora

Enable Outbound Protection In Vista Firewall

Windows Vista comes equiped with two-way firewall, but by default only inbound protection is enabled not to bother inexperienced users with confusing firewall warnings.
Here I will show you how to enable outbound protection to further increase Windows Vista security.
Navigate to start button in left bottom corner and type in“windows firewall with advanced security”. In “Windows Firewall properties” set outbound connection to “block”, according to your firewall policy (home or public). Now when outbound protection is enabled, go to “outbound rules” and add which program you want to be able to access the internet.

By default not even Internet Explorer is able to access Internet with outbound rules set to block.

March 15th, 2009, posted by Erik Klavora

Installing Terminal Services in Application Mode on a Windows 2008 Member Server in a SBS 2008 Domain Succeeds with Errors

http://blogs.technet.com/sbs/archive/2008/10/09/installing-terminal-services-in-application-mode-on-a-windows-2008-member-server-in-a-sbs-2008-domain-succeeds-with-errors.aspx

December 13th, 2008, posted by Petja Mihelj

System State Backups and SBS 2008

The normal backup that SBS 2008 creates contains all the necessary information to restore the entire server. The normal SBS backup includes the system state data. You may wish to create a system state backup of the machine before you make critical changes to the machine or active directory. The ability to take just a system state backup is not exposed in the GUI interface of backup. If you wish to take just a system state backup you must use the wbadmin.exe utility. WBadmin.exe is a command line utility. You must first open a command prompt as administrator.

The command to start a system state backup is:

Wbadmin start systemstatebackup –backuptarget:F:

Where F: is the drive where you wish to store the system state backup.

The target volume for a system state backup cannot be a source volume by default. A source volume is any volume that has a file that is included in the backup. To change that behavior, you can add the AllowSSBToAnyVolume registry entry to the server. However, there are known issues with storing a system state backup on a source volume:

  • Backups can fail. The backup can be modified during the backup process, which might cause the backup to fail.
  • It causes an inefficient use of target space. Twice the amount of space is necessary for a backup than for the original data. The volume must allocate twice the amount of space for the shadow copy process.

The path for adding the new registry entry is as follows:

HKLM\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\AllowSSBToAnyVolume
Type: DWORD
Value: 1

A value of 0 prevents the storing of system state backup on a source volume. A value of 1 allows the storing of system state backup on a source volume.

The backup process will create a directory on the target drive named WindowsImageBackup. This directory will contain the system state backup of the server. The system state backup of an SBS 2008 server is considerably larger than the same backup on an SBS 2003 server. The average system state backup size is around 11GB.

If you wish to restore a system state backup, you must first reboot the server into Directory Services Restore Mode (DSRM). Once in DSRM, you would open a command prompt with administrator rights and use the following commands to start the restore.

We must first determine the version of the backup that you wish to restore.

The command WBADMIN GET VERSIONS will display all the backups on the machine and the version identifier.

The output will look similar to this:

Backup time: 10/7/2008 3:33 PM
Backup target: Fixed Disk labeled D:
Version identifier: 10/07/2008-20:33
Can Recover: Application(s), System State

This backup job was completed on 10/7/2008 at 3:33pm and was saved to drive D:. The backup job has the ability to restore the system state and is version identifier 10/07/2008-20:33

Once we have located the version identifier, we can initiate the restore by using the following command:

WBADMIN START SYSTEMSTATERECOVERY -version: <version id>

Where version id is the version identifier you obtained with the Get Versions command.

For our example the command would be:

WBADMIN START SYSTEMSTATERECOVERY -version: 10/07/2008-20:33

WBADMIN will restore the system state information back to the data from the backup. Once the restore process is complete, you will have to reboot the machine into normal mode to complete the restore.

December 13th, 2008, posted by Petja Mihelj