And things an go wrong !!! Trust me ! I have one or two little inconviences to deal with every now and then because I renamed the machine. But it does beat starting from scratch. ----- Original Message ----- From: "Jim Harrison" <jim@xxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Friday, April 26, 2002 5:01 PM Subject: [isalist] RE: Rename Isa Machi > http://www.ISAserver.org > > > Always trust the voice of the gods... > Officially, ISA server renaming isn't supported and PSS will kindly remind > you of that fact. > Now that I've said that, you can do this successfully, but again; > usupportedly (my word, copyright yesterday, so there). > There are two registry entries that govern how ISA "views itself": > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fpc\Arrays\{GUID}\Servers\{GUID}] > "msFPCName"="WINSname" > "msFPCFQDN"="server.domain.tld" > > There are similar entries in AD for array members, but since I don't have > one handy, you'll just have to search them out. > > Jim Harrison > MCP(NT4, W2K), A+, Network+, PCG > http://isaserver.org/authors/harrison/ > Read the books! > ----- Original Message ----- > From: "Deus, Attonbitus" <Thor@xxxxxxxxxxxxxxx> > To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> > Sent: Thursday, April 25, 2002 9:52 AM > Subject: [isalist] RE: Rename Isa Machi > > > http://www.ISAserver.org > > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > At 09:35 AM 4/25/2002, Steve Moffat wrote: > >You can't > > > >I renamed ISA Server and all services on Isa is uniavaliable and it's with > >old name. > >How can I to rename ISA Server Machine ? > > > >Thanks > > > > > Jim and I briefly discussed this once during a past thread and I would like > to make some comments... > I have renamed my ISA servers a couple of different times without > issues. Others have had issues, and I am not sure why. > > My gut feeling is that if the box is a standalone install, one can perform > the rename function as one would normally rename a domain > member. Obviously, firewall configurations or Web Proxy configurations > would also need to updated to reflect the new name. > > If it is an enterprise configuration where Active Directory schema has been > updated and entries made to the AD, one would have to use ADSIEdit or other > to ensure that the Active Directory entries were properly updated as well. > > If someone has time, I think it would be valuable to fully test what > different renaming scenarios entail as the issue has arisen here several > times... > > Also, I would like to know about other experiences with this to see if we > can get an accurate picture of what is happening... But IIRC, Jim stated > that renaming the server was "not a supported feature" of ISA... > > > AD > > > > -----BEGIN PGP SIGNATURE----- > Version: PGP 7.1 > > iQA/AwUBPMg0TIhsmyD15h5gEQIK9gCgh4WC4TXmHDl6HXeZQNXEZbtHW+wAoOYx > /vLY7JEigmcuiSkVJ3mDkK7v > =6hhi > -----END PGP SIGNATURE----- > > > ------------------------------------------------------ > You are currently subscribed to this ISAserver.org Discussion List as: > jim@xxxxxxxxxxxx > To unsubscribe send a blank email to $subst('Email.Unsub') > > > > ------------------------------------------------------ > You are currently subscribed to this ISAserver.org Discussion List as: strangconst@xxxxxxxxxx > To unsubscribe send a blank email to $subst('Email.Unsub')