Yep, only a C: Drive. Customer had their cousin setup the server and when they got done with the wizards they couldn't figure anything else out. He already manually joined about 20 machines to the domain and imported each of their mailboxes, etc. Customer will not pay for us to rebuild the server properly so now its patching it up. This is the last part was their offsite backup, which does not support 2008 yet.
I also liked the vocabulary...Shook may have to roll to dictionary.com though to understand it. Greg From: Michael B. Smith [mailto:[email protected]] Sent: Wednesday, January 14, 2009 9:41 PM To: NT System Admin Issues Subject: RE: Server 2008 GUID for backup devices Can you elucidate a little bit? You mean that you only have a C:\ ? Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php From: [email protected] [mailto:[email protected]] Sent: Wednesday, January 14, 2009 6:20 PM To: NT System Admin Issues Subject: Server 2008 GUID for backup devices Well those of you running 2008 for sure know that the native backup tools in 08 have been significantly altered and you can no longer perform system state to "critical volumes" This presents a problem for applications that replicate offsite by creating a systemstate file locally and sending it off, or for clients that send systemstate volumes to network locations for backup. My specific question is.. "Does anyone know how to make Server 08 present a network drive or remapped path on an existing volume as a NEW GUID volume to the OS. Subst command does not present a GUID for the volume you map according to a WMI lookup of Win32_volume We are trying to work around this until the software vendors come out with a workaround or MS provides some kind of interface for doing this again. Thanks Greg Sweers ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
