Nope.. All disks have signatures including basic disks. Joe _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Luchette, Jon Sent: Monday, November 07, 2005 12:03 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Cloning with Remapped Drives But disk signatures only get written to dynamic disks right? Our drives are basic disks... _______________________________________________ Jon Luchette Emerson Hospital Technology Specialist III Work: 978-287-3369 Cell: 978-360-1379 jluchette@xxxxxxxxxxxxxxx _______________________________________________ _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Monday, November 07, 2005 12:25 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Cloning with Remapped Drives The key is the drive signature. If it changes, windows will not be able associate the remapped drive letter to the disk/volume. Joe _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Luchette, Jon Sent: Monday, November 07, 2005 10:09 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Cloning with Remapped Drives We have been trying to use Sysprep and the SnapClones feature of an EVA 5000 SAN, but haven't had any luck. We know that HP's Rapid Deployment Pack (RDP) will work, but that runs over the network so it'll take around 20-30 minutes. We are now looking into using a snapclone and then using a sidchanger utility like NEWSID, because that might save us some time. If it works we may potentially be able to bring up a new server in 2 to 3 minutes. I have heard of the same switch using Ghost, but GHOST would operate like RDP over the network. _______________________________________________ Jon Luchette Emerson Hospital Technology Specialist III Work: 978-287-3369 Cell: 978-360-1379 jluchette@xxxxxxxxxxxxxxx _______________________________________________ _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Dirk Blose Sent: Monday, November 07, 2005 11:58 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Cloning with Remapped Drives What are you using to clone the drives? If I remember correctly there is a switch for ghost to force it to retain the drive remapping when cloning the disk. Dirk Blose, MCSE, CCA Lead Technical Analyst (919) 765-4791 dirk.blose@xxxxxxxxxx >>> JLuchette@xxxxxxxxxxxxxxx 11/07/05 11:43 AM >>> No unfortunately not, we have tried that and it'll bomb out with an error. I don't have the exact error message handy, I apologize. Thank you though... _______________________________________________ Jon Luchette Emerson Hospital Technology Specialist III Work: 978-287-3369 Cell: 978-360-1379 jluchette@xxxxxxxxxxxxxxx _______________________________________________ -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] <mailto:thin-bounce@xxxxxxxxxxxxx%5d> On Behalf Of Tom Howarth Sent: Monday, November 07, 2005 11:24 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Cloning with Remapped Drives can you not just try to run the remap drives utility, to change the mappings again. this could be do-able by adding [GuiRunOnce] ;use this line to run a command when the mini install wizard runs Command0 = "path to drive remap utiltiy" again I have not checked this, it is only a suposition. On 07/11/05, Luchette, Jon <JLuchette@xxxxxxxxxxxxxxx> wrote: > What happens is after we capture the sysprepped image on the server > that we have changed the drive letters on, for example C: and D: are > now U: and V:, and we blow it down to the new server, the new server > comes up with C: and > D: instead of U: and V: and we get the following error: > > > "The logon user interface dll ctxgina.dll failed to load. " > > > > What is the solution that you are referring to? I will give it a shot... > > > > Thanks! > > > _______________________________________________ > Jon Luchette > Emerson Hospital > Technology Specialist III > Work: 978-287-3369 > Cell: 978-360-1379 > > > jluchette@xxxxxxxxxxxxxxx > _______________________________________________ > > > ________________________________ > From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] <mailto:thin-bounce@xxxxxxxxxxxxx%5d> On > Behalf Of Michel Roth > Sent: Monday, November 07, 2005 3:43 AM > > To: thin@xxxxxxxxxxxxx > Subject: [THIN] Re: Cloning with Remapped Drives > > > In what way does it not work? If it's drive letter assignment after > the imaging that's the problem then there's a solution. > > 2005/11/5, Luchette, Jon <JLuchette@xxxxxxxxxxxxxxx>: > > >>>>>>>>>>using sysprep in conjunction with snapclones on our EVA > > >>>>>>>>>>SAN we > can deploy an OS to a blade in about 2 or 3 minutes. Unfortunately, > this second option doesn't seem to work with Citrix and remapped drives. > > > > > > > > ________________________________ > > > > From: thin-bounce@xxxxxxxxxxxxx on behalf of M > > Sent: Fri 11/4/2005 6:02 PM > > To: thin@xxxxxxxxxxxxx > > Subject: [THIN] Re: Cloning with Remapped Drives > > > > > > Crikey ... how are you managing the Blades ? > > RDP is a great way to deploy operating systems and apps to your > > Blades > along with managing them. > > > > BTW version 2.2 is out and available from the HP RDP website. > > > http://h18013.www1.hp.com/products/servers/management/rdp/rdp-dl.html > > > > Your enclosure licenses will be valid > > > > > > ----- Original Message ----- > > From: Luchette, Jon <mailto:JLuchette@xxxxxxxxxxxxxxx> > > To: thin@xxxxxxxxxxxxx > > Sent: Friday, November 04, 2005 10:45 PM > > Subject: RE: [THIN] Re: Cloning with Remapped Drives > > > > We haven't tried RDP yet, we were trying to use Sysprep when > > we > encountered the problem. We'll just try RDP then, it sounds like it > should work... > > > > Does anyone know of a way to make sysprep work? Just curious? > > > > Thanks! > > > > ________________________________ > > > > From: thin-bounce@xxxxxxxxxxxxx on behalf of M > > Sent: Fri 11/4/2005 5:09 PM > > To: thin@xxxxxxxxxxxxx > > Subject: [THIN] Re: Cloning with Remapped Drives > > > > > > What issues are you having with RDP and remapped drives ? > > > > RDP has supported cloning with remapped drives since an > > Altiris DS > patch for 1.5 was released last year. > > > http://h18013.www1.hp.com/products/servers/management/rdp/knowledgebas > e/00000122.html > > > > > > > > > > ----- Original Message ----- > > From: Luchette, Jon <mailto: JLuchette@xxxxxxxxxxxxxxx> > > To: thin@xxxxxxxxxxxxx > > Sent: Friday, November 04, 2005 8:41 PM > > Subject: [THIN] Cloning with Remapped Drives > > > > Hello, we are running 8 MF XP FR3 servers with sp4. > > The > Operating System is Windows 2003 server sp1. These are HP blade > servers that currently boot from our SAN. We are trying to develop an > effective cloning strategy but have run into the issue from having > remapped drive letters (U: and V:). I know that this has been > discussed on this list in the past and I thought there was some type of solution that works now, but I > cannot remember for sure what is was. What are people doing to get around > this issue? We have licensing for HP's RDP (rapid deployment pack), > but if you know of other solutions that work, please let me know as well. > > > > Thanks in advance for your replies! > > > > > > > _______________________________________________ > > Jon Luchette > > > > Emerson Hospital > > Technology Specialist III > > > > Work: 978-287-3369 > > Cell: 978-360-1379 > > > > jluchette@xxxxxxxxxxxxxxx > > > _______________________________________________ > > > > > > > > > > > > > > -- Tom at home ************************************************ For Archives, RSS, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: //www.freelists.org/list/thin ************************************************ ************************************************ For Archives, RSS, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: //www.freelists.org/list/thin ************************************************