Posts Tagged ‘Server 2008’

Server 2008 with Hyper-V Hangs after login or startup for an extended period of time then resumes normal operation.

April 19th, 2012

I recently ran into an issue where my 2008 Hyper-V hosts would reboot, get to the login prompt then after the login prompt either hang at the welcome screen or login fine and operate normally for a minute or two then lock up for 30-45 minutes. If I had enough time to start the virtual machines on the box, they would run fine in the background, you just could not do anything on the console or login remotely to the machine.  You could ping and connect to the file system remotely but that was the extent of the remote services available.

After searching long and hard to find a solution I ran across the following blog which explained my exact problem:

I run NetBackup and leverage VSS snapshots for backups.  These 2008 boxes have been in commission for quite a while and have amassed 3-4K orphaned devices.

There is an 2008 R2 hotfix out there for this issue:

However this hotfix does not install on 2008 R1. I had to track down the DevNodeClean utility which Microsoft does not distribute. I found and tested this on a test server which worked great.


DevNodeClean Utility Instructions:

Usage: DevNodeClean /r /l /?

/r displays removes the phantom device nodes. Otherwise only shows what will be removed
/l displays all device nodes including non-phantom. Does not remove unless -r is also included.
(Only phantom devices are ever removed.)
/? displays this help screen

Must be run as administrator
Backup and Restore privileges are required to run this utility.

Download:   DevNodeClean-x64   or  DevNodeClean-x32

Tags: ,
Posted in Uncategorized | Comments (0)

Using Diskshadow to delete Shadow Copies on Server 2008

March 9th, 2012

If you run into a case where you need to list the shadow copies on a drive or you have a shadow copy that has become orphaned, the following can be used on Server 2008 to remove those shadow copies. This is done from the standard cmd prompt.


>list shadows all


>delete shadows id 36350cd8-5ae2-4ccc-a9e3-e0db64116883 => The ID of the shadow you want to delete if you have multiple and want to remove one.


>delete shadows all => To delete them all if the only ones listed are the ones you want to delete.


Tags: ,
Posted in Uncategorized | Comments (0)

Netbackup 7.1 GRT Exchange 2010 Restore

November 17th, 2011

After implementing granular restore (GRT) for Exchange 2010 on netbackup, I had the opportunity to test restoring of all items in someones inbox.  Below are all of the things that needed to be done in order for this to work for me.  A couple of important things that need to be understood in order to do a GRT Restore.

My Config:
Server 2008
1 -CAS Server
3-Mailbox/Database Servers (stand alone, no dags)
1-Hub Transport
1-Edge Transport

Important Concepts:

*Read the manual:
The restore is done to the CAS server not the mailbox/database server.  So in netbackup when you select the source client, you choose the mailbox server.  In the destination client you need to choose your CAS server.
*In order to accomplish the above, you will need to have the netbackup client installed on your CAS server.  You will also need the netbackup services  (client service, and legacy client service) running under the same credentials as the services are running under on your database/mailbox server.  Below is the relevant information from the netbackup exchange server administrator’s guide on setting up the service account.
*The CAS server needs to be able to see the backups, so on the CAS server if you cannot browse the backups for your mailbox server, you will need to change the configuration on the master server so that the CAS server can see these backups.
*Network File Services is required on the CAS Server in order to coordinate the restore.
*For GRT restores that are individual folders or items you DO NOT need to dismount your database, it will happily do this online.  If you try to restore an entire mailbox, you will need to dismount.


How to configure Netbackup and your Exchange Infrastructure to restore GRT items.

1 – Install NFS on CAS Server.

This is done through the server manager using the add role.   Click add roles, choose file services, on the next screen choose Services for Network File System. This will add the necessary information.  For security reasons, you can disable the Server for NFS service.  You must leave the Client for NFS service enabled.

2 – Install Client on CAS Server

Make sure that you install the client at the same patch level and version as the master server and the mailbox server.

Once it is installed you will need to change the service logon account.  (See below if you have not set this up yet, you should have though if you are successfully doing a GRT backup: Configuring the NetBackup service account (Exchange 2010))

3- Enable Impersonation

This step is extremely important.  The service account needs to be able to proxy every account otherwise it cannot connect to the mailbox.  So this command is allowing your service account to impersonate a user in order to restore the messages.

From the Exchange Management Shell:
New-ManagementRole -Name EWSImpersonationRole -Parent ApplicationImpersonation

New-ManagementRoleAssignment -Role EWSImpersonationRole -User {Your Service Account} EWSImpersonationRoleAssignment 

3 – Add policy for CAS Server.

On your netbackup master server, you will want to create a policy for your CAS server in order for netbackup to know that your CAS server exists.  You can just create a blank policy without a schedule.

4 – Distributed Application Restore Mapping

This is another important one as it ties your CAS server to your database/mailbox server.  In the Master Servers Host Properties, you need to go to the Distributed Application Restore Mapping property and add entries for each of your mailbox/database servers cross referenced to your CAS server.  The application host is your mailbox/db server, the component host is your CAS Server.  You should create this with the FQDN as well as the NetBIOS names.

5 – Enable Browsing

To make sure that the CAS Server can access the backups, there are two things to check.  In the Master Server’s Host Properties, choose Client Attributes and make sure that in the Global Client Attributes that Allow is checked for both. Otherwise you will need to add the CAS server and enable both in the browse and restore ability section.

If it works for your environment, you should also add the following on the master server.  Create the altnames directory in the following folder (or the equivalent folder based on your install path of netbackup): C:\Program Files\Veritas\NetBackup\db\

create a file called No.Restrictions (empty file without extension)
This allows all clients to browse all backups. Use at your own risk.  If you have a managed infrastructure with multiple individuals doing backups/restores with permissions based on what servers they have access to, you might want to research this one a little more.


Configuring the NetBackup service account (Exchange 2010)

1 In Active Directory Users and Computers, select the Users directory.

2 Right-click on the Administrator account, click Copy, and create an account for NetBackup. Create a user account that has a mailbox with a unique name. A unique name is one that does not already exist within the Exchange Organization. This name cannot be contained as a set of characters in an existing name. For example: EXCH1 is entered as the unique mailbox name, and other mailbox names such asEXCH1BACKUPorBACKUPEXCH1exist. The backup or restore of individual mailboxes or both fail.

3 Double-click on the account you created.

4 In the Properties dialog box, click the Members Of tab.

5 ClickAddand add this account to the following groups ■Domain Admins group ■ Administrators ■ Domain Users ■ Organization Management

6 Configure the NetBackup Client Service log on account. See “Symantec NetBackup for Microsoft Exchange Server Administrator’s Guide: Configuring the log on account for the NetBackup Client Service” on page 57.


Sites that I found much of this information on:


Errors that you might encounter if the above is not configured correctly:

-file read failed status code 13
-RBAC exchange grt
-“RBAC authorization returns Access Denied for user  Reason: No role assignments associated with the specified user were found on Domain Controller ” (For this error make sure that you complete step 3 above)
-Windows(R) Lightweight Directory Access Protocol (LDAP) failed a request to connect to Active Directory Domain Services(R) for Windows user (This error will show up in your event log, research shows that you can safely ignore this)
– rai error = 6 (I fixed this error with #3)
-restore unable to create object
– bpbrm unable to create object
-error 29 – GRE EXITING WITH STATUS = 29
-Error bpbrm() client restore EXIT STATUS 13: file read failed
-FTL – tar file write error (0)
-ms-exchange-server policy restore error 2810

Tags: , ,
Posted in Uncategorized | Comments (1)

Setting Printer Preferences

November 8th, 2011

I have a printer on my Windows 2008 Print Server that despite many attemps and approaching the situation from different ways, I cannot get the preferences that I set on the Print Server to be shared with the rest of the clients.  It is possible that this is a 64-bit/32-bit issue since my server is 64 bit and my clients are Windows 7 32 bit.  We also had to use the Vista driver since there is not a suitable Server 2008/Win 7 Driver.  (The printer in question is a HP DesignJet 1050C ) So after trying to set the preferences from a Win 7 station and that not taking, I figured I would have to find the actual preferences and somehow deploy those.  Surprisingly, there is not a lot of information about location of print preferences, manually replicating print preferences, or otherwise copying/deploying these print preferences.  Here is how I ended up accomplishing this:

This was the big aha moment, it is all stored in the registry and the preferences are all stored in a single binary value. I had found some articles pointing to this location in the registry, but none of them explained the importance of the DevMode binary value.  Source:

1) Create and Export Registry Key:  So on one of the client computers, I set all of the printing preferences settings then proceeded to export the key.  (Important Note: in the key there is a server value that you will want to inspect.  Make sure that if you are going to map this through a FQDN then your server name will need to match here.)  This file will need to be copied to a location that everyone that will map this printer and need its settings, has access to.  (Sysvol on the domain is a potential good place as everyone has access to it, in my case I have a share on one of my file servers that has other reg files that I deploy so I chose this location.)

2) Create Group Policy: I created a group policy that basically would copy the .reg to a folder on the client, copy a .bat file that I created to the windows start menu, and create a folder for the preceding file to reside in.  This is deployed in the computer configuration so that the files will be copied to the computer before a user logs in.

For the group policy:
– Computer Configuration -> Preferences -> Windows Settings -> Files (.reg file that will be copied to the folder below. Example: printer.reg)
– Computer Configuration -> Preferences -> Windows Settings ->Folders (This one will create the folder for your .reg File Example: c:\printprefs)
– Computer Configuration -> Preferences -> Windows Settings -> Files (.bat file (Example printpref.bat)created in same directory as .reg file copied to start menu: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ )

*** The .bat file would have the following line in it based on the examples above:
reg import c:\printprefs\printer.reg

3) Test: You should be able to restart a computer with this policy and see a folder created, with a .reg file in it.  If you look in the start menu under startup, there should be a .bat file in there that calls the reg file.  You should be able to look at your printers preferences and everything that you set should be not set on the new client.

There is likely more elegant ways to do this, like build the registry key and values through group policy.  But I think that this is more managable as I just have to update one .reg file if the preferences need to change and it is automatically updated on all computers with that group policy without having to modify the group policy.   This is also NOT the standard way to deploy preferences.  You should just be able to jump on the print server open the printer properties, go to the advanced tab, and set the printing defaults. However when that fails like in my case, the above works….


Keywords (these are all of the things I tried googling to come up with this and found very few results….):
Server 2008 print server not saving preferences
duplicating print preferences.
duplicating printing preferences
Deploying printing preferences through group policy
Location of printer preferences
Location of printing preferences
printer preferences not saving

Tags: , ,
Posted in Uncategorized | Comments (0)

Adding stsadm to path for easy access on MOSS 2007

October 7th, 2011

On your MOSS 2007/WSS 3 server you will probably want to add the following to your path variable in order to access the stsadm command without having to navigate into that folder.

1 – right click on computer and go to properties.  
2- For Server 2008 choose advanced system settings.
3 -For Server 2003 & 2008 choose Advanced
4 – Click Environment Variables.
5- Under System Variables find “PATH” and click edit
6- go to the end of the string, add a semi-colon and then copy and paste the following in: c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin 
7 – save out.  Now when you open the command prompt, you just have to type stsadm to get to your command.

Tags: , ,
Posted in Uncategorized | Comments (0)