RE: Rename 2003 domain
Don't rename the domain. Just Say No. There is no need. Sent from my Windows Phone From: David Mazzaccaro Sent: 2/1/2013 9:50 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate…. But it doesn’t go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use “company.com” on in the internet. So if we never use “company.NET” on the outside, why couldn’t/shouldn’t I rename the domain to that? Thx From: Webster [mailto:webs...@carlwebster.com] Sent: Friday, February 01, 2013 12:23 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Go to the archives and read the “SSL and the new no internal names ruling” thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name “company.town.main” It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So… I will be renaming the domain to “company.net” this weekend. I have already registered the “company.net” name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: “XDR-fixup” Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%ifile:///\\%25%25i -f -r -t 05 My question is… has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha’s that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: Rename 2003 domain
We hired a consultant to move us to AD 2008 R2 and E2010. He renamed the domain to company.net this past weekend. We did have to manually rejoin the clients to the new domain (rebooting twice did not make the clients auto-join), but everything appears to be working fine. We have just extended the schema and have our first 2008 R2 domain controller up and running. Anything in particular I should check to verify that all is well? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 9:50 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain Don't rename the domain. Just Say No. There is no need. Sent from my Windows Phone From: David Mazzaccaro Sent: 2/1/2013 9:50 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate But it doesn't go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use company.com on in the internet. So if we never use company.NET on the outside, why couldn't/shouldn't I rename the domain to that? Thx From: Webster [mailto:webs...@carlwebster.com] Sent: Friday, February 01, 2013 12:23 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Go to the archives and read the SSL and the new no internal names ruling thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name company.town.main It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So... I will be renaming the domain to company.net this weekend. I have already registered the company.net name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: XDR-fixup Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%i file:///\\%25%25i -f -r -t 05 My question is... has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha's that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: Rename 2003 domain
To add to Michael's point, this wasn't necessary and probably wasn't the best idea. The consultant obviously messed something up given you had to rejoin clients. The simple fact that the consultant was happy to (and possibly recommended) this domain rename tells me a lot. Thanks, Brian Desmond br...@briandesmond.commailto:br...@briandesmond.com w - 312.625.1438 | c - 312.731.3132 From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Tuesday, February 5, 2013 9:55 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain We hired a consultant to move us to AD 2008 R2 and E2010. He renamed the domain to company.net this past weekend. We did have to manually rejoin the clients to the new domain (rebooting twice did not make the clients auto-join), but everything appears to be working fine. We have just extended the schema and have our first 2008 R2 domain controller up and running. Anything in particular I should check to verify that all is well? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 9:50 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain Don't rename the domain. Just Say No. There is no need. Sent from my Windows Phone From: David Mazzaccaro Sent: 2/1/2013 9:50 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate But it doesn't go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use company.com on in the internet. So if we never use company.NET on the outside, why couldn't/shouldn't I rename the domain to that? Thx From: Webster [mailto:webs...@carlwebster.com] Sent: Friday, February 01, 2013 12:23 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Go to the archives and read the SSL and the new no internal names ruling thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name company.town.main It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So... I will be renaming the domain to company.net this weekend. I have already registered the company.net name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: XDR-fixup Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%ifile:///\\%25%25i -f -r -t 05 My question is... has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha's that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe
RE: Rename 2003 domain
To the OP: you already know your domain is broken. Good luck. You are going to need it. From: Brian Desmond [mailto:br...@briandesmond.com] Sent: Tuesday, February 5, 2013 1:29 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain To add to Michael's point, this wasn't necessary and probably wasn't the best idea. The consultant obviously messed something up given you had to rejoin clients. The simple fact that the consultant was happy to (and possibly recommended) this domain rename tells me a lot. Thanks, Brian Desmond br...@briandesmond.commailto:br...@briandesmond.com w - 312.625.1438 | c - 312.731.3132 From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Tuesday, February 5, 2013 9:55 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain We hired a consultant to move us to AD 2008 R2 and E2010. He renamed the domain to company.net this past weekend. We did have to manually rejoin the clients to the new domain (rebooting twice did not make the clients auto-join), but everything appears to be working fine. We have just extended the schema and have our first 2008 R2 domain controller up and running. Anything in particular I should check to verify that all is well? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 9:50 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain Don't rename the domain. Just Say No. There is no need. Sent from my Windows Phone From: David Mazzaccaro Sent: 2/1/2013 9:50 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate But it doesn't go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use company.com on in the internet. So if we never use company.NET on the outside, why couldn't/shouldn't I rename the domain to that? Thx From: Webster [mailto:webs...@carlwebster.com] Sent: Friday, February 01, 2013 12:23 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Go to the archives and read the SSL and the new no internal names ruling thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name company.town.main It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So... I will be renaming the domain to company.net this weekend. I have already registered the company.net name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: XDR-fixup Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%ifile:///\\%25%25i -f -r -t 05 My question is... has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha's that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog
RE: Rename 2003 domain
Wow, Webster Desmond and MBS recommend against it. ...and I thought a couple of SBS swings were high on the things could go horribly wrong scale... From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 10:36 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain To the OP: you already know your domain is broken. Good luck. You are going to need it. From: Brian Desmond [mailto:br...@briandesmond.com] Sent: Tuesday, February 5, 2013 1:29 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain To add to Michael's point, this wasn't necessary and probably wasn't the best idea. The consultant obviously messed something up given you had to rejoin clients. The simple fact that the consultant was happy to (and possibly recommended) this domain rename tells me a lot. Thanks, Brian Desmond br...@briandesmond.commailto:br...@briandesmond.com w - 312.625.1438 | c - 312.731.3132 From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Tuesday, February 5, 2013 9:55 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain We hired a consultant to move us to AD 2008 R2 and E2010. He renamed the domain to company.net this past weekend. We did have to manually rejoin the clients to the new domain (rebooting twice did not make the clients auto-join), but everything appears to be working fine. We have just extended the schema and have our first 2008 R2 domain controller up and running. Anything in particular I should check to verify that all is well? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 9:50 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain Don't rename the domain. Just Say No. There is no need. Sent from my Windows Phone From: David Mazzaccaro Sent: 2/1/2013 9:50 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate But it doesn't go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use company.com on in the internet. So if we never use company.NET on the outside, why couldn't/shouldn't I rename the domain to that? Thx From: Webster [mailto:webs...@carlwebster.com] Sent: Friday, February 01, 2013 12:23 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Go to the archives and read the SSL and the new no internal names ruling thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name company.town.main It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So... I will be renaming the domain to company.net this weekend. I have already registered the company.net name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: XDR-fixup Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%ifile:///\\%25%25i -f -r -t 05 My question is... has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha's that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE
RE: Rename 2003 domain
My name doesn't belong in the same sentence as Desmond and MBS. My name should have appeared in subscript! :) Carl Webster Consultant and Citrix Technology Professional http://www.CarlWebster.comhttp://www.carlwebster.com/ From: David Lum [mailto:david@nwea.org] Sent: Tuesday, February 05, 2013 1:46 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Wow, Webster Desmond and MBS recommend against it. ...and I thought a couple of SBS swings were high on the things could go horribly wrong scale... From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 10:36 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain To the OP: you already know your domain is broken. Good luck. You are going to need it. From: Brian Desmond [mailto:br...@briandesmond.com] Sent: Tuesday, February 5, 2013 1:29 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain To add to Michael's point, this wasn't necessary and probably wasn't the best idea. The consultant obviously messed something up given you had to rejoin clients. The simple fact that the consultant was happy to (and possibly recommended) this domain rename tells me a lot. Thanks, Brian Desmond br...@briandesmond.commailto:br...@briandesmond.com w - 312.625.1438 | c - 312.731.3132 From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Tuesday, February 5, 2013 9:55 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain We hired a consultant to move us to AD 2008 R2 and E2010. He renamed the domain to company.net this past weekend. We did have to manually rejoin the clients to the new domain (rebooting twice did not make the clients auto-join), but everything appears to be working fine. We have just extended the schema and have our first 2008 R2 domain controller up and running. Anything in particular I should check to verify that all is well? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 9:50 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain Don't rename the domain. Just Say No. There is no need. Sent from my Windows Phone From: David Mazzaccaro Sent: 2/1/2013 9:50 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate But it doesn't go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use company.com on in the internet. So if we never use company.NET on the outside, why couldn't/shouldn't I rename the domain to that? Thx From: Webster [mailto:webs...@carlwebster.com] Sent: Friday, February 01, 2013 12:23 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Go to the archives and read the SSL and the new no internal names ruling thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name company.town.main It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So... I will be renaming the domain to company.net this weekend. I have already registered the company.net name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: XDR-fixup Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%ifile:///\\%25%25i -f -r -t 05 My question is... has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha's that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
Re: Rename 2003 domain
Footnotes are more typically done with superscripts. Just sayin' :) Kurt On Tue, Feb 5, 2013 at 12:33 PM, Webster webs...@carlwebster.com wrote: My name doesn’t belong in the same sentence as “Desmond and MBS”. My name should have appeared in subscript! J Carl Webster Consultant and Citrix Technology Professional http://www.CarlWebster.com From: David Lum [mailto:david@nwea.org] Sent: Tuesday, February 05, 2013 1:46 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Wow, Webster Desmond and MBS recommend against it. …and I thought a couple of SBS swings were high on the “things could go horribly wrong” scale… From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 10:36 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain To the OP: you already know your domain is broken. Good luck. You are going to need it. From: Brian Desmond [mailto:br...@briandesmond.com] Sent: Tuesday, February 5, 2013 1:29 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain To add to Michael’s point, this wasn’t necessary and probably wasn’t the best idea. The consultant obviously messed something up given you had to rejoin clients. The simple fact that the consultant was happy to (and possibly recommended) this domain rename tells me a lot. Thanks, Brian Desmond br...@briandesmond.com w – 312.625.1438 | c – 312.731.3132 From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Tuesday, February 5, 2013 9:55 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain We hired a consultant to move us to AD 2008 R2 and E2010. He renamed the domain to company.net this past weekend. We did have to manually rejoin the clients to the new domain (rebooting twice did not make the clients auto-join), but everything appears to be working fine. We have just extended the schema and have our first 2008 R2 domain controller up and running. Anything in particular I should check to verify that all is well? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 9:50 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain Don't rename the domain. Just Say No. There is no need. Sent from my Windows Phone From: David Mazzaccaro Sent: 2/1/2013 9:50 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate…. But it doesn’t go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use “company.com” on in the internet. So if we never use “company.NET” on the outside, why couldn’t/shouldn’t I rename the domain to that? Thx From: Webster [mailto:webs...@carlwebster.com] Sent: Friday, February 01, 2013 12:23 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Go to the archives and read the “SSL and the new no internal names ruling” thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name “company.town.main” It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So… I will be renaming the domain to “company.net” this weekend. I have already registered the “company.net” name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: “XDR-fixup” Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%i -f -r -t 05 My question is… has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha’s that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com
RE: Rename 2003 domain
Pffft. You are known world-wide (literally) as the Citrix AD Expert. If there is any name that doesn't belong on that list, it is mine. From: Webster [mailto:webs...@carlwebster.com] Sent: Tuesday, February 5, 2013 3:33 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain My name doesn't belong in the same sentence as Desmond and MBS. My name should have appeared in subscript! :) Carl Webster Consultant and Citrix Technology Professional http://www.CarlWebster.comhttp://www.carlwebster.com/ From: David Lum [mailto:david@nwea.org] Sent: Tuesday, February 05, 2013 1:46 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Wow, Webster Desmond and MBS recommend against it. ...and I thought a couple of SBS swings were high on the things could go horribly wrong scale... From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 10:36 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain To the OP: you already know your domain is broken. Good luck. You are going to need it. From: Brian Desmond [mailto:br...@briandesmond.com] Sent: Tuesday, February 5, 2013 1:29 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain To add to Michael's point, this wasn't necessary and probably wasn't the best idea. The consultant obviously messed something up given you had to rejoin clients. The simple fact that the consultant was happy to (and possibly recommended) this domain rename tells me a lot. Thanks, Brian Desmond br...@briandesmond.commailto:br...@briandesmond.com w - 312.625.1438 | c - 312.731.3132 From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Tuesday, February 5, 2013 9:55 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain We hired a consultant to move us to AD 2008 R2 and E2010. He renamed the domain to company.net this past weekend. We did have to manually rejoin the clients to the new domain (rebooting twice did not make the clients auto-join), but everything appears to be working fine. We have just extended the schema and have our first 2008 R2 domain controller up and running. Anything in particular I should check to verify that all is well? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 05, 2013 9:50 AM To: NT System Admin Issues Subject: RE: Rename 2003 domain Don't rename the domain. Just Say No. There is no need. Sent from my Windows Phone From: David Mazzaccaro Sent: 2/1/2013 9:50 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate But it doesn't go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use company.com on in the internet. So if we never use company.NET on the outside, why couldn't/shouldn't I rename the domain to that? Thx From: Webster [mailto:webs...@carlwebster.com] Sent: Friday, February 01, 2013 12:23 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Go to the archives and read the SSL and the new no internal names ruling thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name company.town.main It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So... I will be renaming the domain to company.net this weekend. I have already registered the company.net name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: XDR-fixup Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%ifile:///\\%25%25i -f -r -t 05 My question is... has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha's that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt
RE: Rename 2003 domain
But compared to Desmond and MBS, superscript would have put my name higher than theirs and it should be lower (much lower) so subscript, in this one case, should be used. Thanks Webster -Original Message- From: Kurt Buff [mailto:kurt.b...@gmail.com] Sent: Tuesday, February 05, 2013 3:23 PM To: NT System Admin Issues Subject: Re: Rename 2003 domain Footnotes are more typically done with superscripts. Just sayin' :) Kurt On Tue, Feb 5, 2013 at 12:33 PM, Webster webs...@carlwebster.com wrote: My name doesn’t belong in the same sentence as “Desmond and MBS”. My name should have appeared in subscript! J From: David Lum [mailto:david@nwea.org] Sent: Tuesday, February 05, 2013 1:46 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Wow, Webster Desmond and MBS recommend against it. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
Re: Rename 2003 domain
There's only so much genuflecting I can take in a single thread, so cut it out, or i'll send both of you to your rooms (Citrix and Microsoft, respectively) *ASB **http://XeeMe.com/AndrewBaker* http://xeeme.com/AndrewBaker* **Providing Virtual CIO Services (IT Operations Information Security) for the SMB market…*** On Tue, Feb 5, 2013 at 4:29 PM, Michael B. Smith mich...@smithcons.comwrote: Pffft. You are known world-wide (literally) as the Citrix AD Expert. ** ** If there is any name that doesn’t belong on that list, it is mine. ** ** *From:* Webster [mailto:webs...@carlwebster.com] *Sent:* Tuesday, February 5, 2013 3:33 PM *To:* NT System Admin Issues *Subject:* RE: Rename 2003 domain ** ** My name doesn’t belong in the same sentence as “Desmond and MBS”. My name should have appeared in subscript! J ** ** Carl Webster Consultant and Citrix Technology Professional http://www.CarlWebster.com http://www.carlwebster.com/ ** ** ** ** *From:* David Lum [mailto:david@nwea.org david@nwea.org] *Sent:* Tuesday, February 05, 2013 1:46 PM *To:* NT System Admin Issues *Subject:* RE: Rename 2003 domain ** ** Wow, Webster Desmond and MBS recommend against it. ** ** …and I thought a couple of SBS swings were high on the “things could go horribly wrong” scale… ** ** *From:* Michael B. Smith [mailto:mich...@smithcons.commich...@smithcons.com] *Sent:* Tuesday, February 05, 2013 10:36 AM *To:* NT System Admin Issues *Subject:* RE: Rename 2003 domain ** ** To the OP: you already know your domain is broken. ** ** Good luck. You are going to need it. ** ** *From:* Brian Desmond [mailto:br...@briandesmond.combr...@briandesmond.com] *Sent:* Tuesday, February 5, 2013 1:29 PM *To:* NT System Admin Issues *Subject:* RE: Rename 2003 domain ** ** *To add to Michael’s point, this wasn’t necessary and probably wasn’t the best idea. The consultant obviously messed something up given you had to rejoin clients. The simple fact that the consultant was happy to (and possibly recommended) this domain rename tells me a lot. * * * *Thanks,* *Brian Desmond* *br...@briandesmond.com* * * *w – 312.625.1438 | c – 312.731.3132* * * *From:* David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.comdavid.mazzacc...@hudsonmobility.com] *Sent:* Tuesday, February 5, 2013 9:55 AM *To:* NT System Admin Issues *Subject:* RE: Rename 2003 domain ** ** We hired a consultant to move us to AD 2008 R2 and E2010. He renamed the domain to company.net this past weekend. We did have to manually rejoin the clients to the new domain (rebooting twice did not make the clients auto-join), but everything appears to be working fine. We have just extended the schema and have our first 2008 R2 domain controller up and running. ** ** Anything in particular I should check to verify that all is well? ** ** ** ** ** ** ** ** ** ** ** ** *From:* Michael B. Smith [mailto:mich...@smithcons.commich...@smithcons.com] *Sent:* Tuesday, February 05, 2013 9:50 AM *To:* NT System Admin Issues *Subject:* RE: Rename 2003 domain ** ** Don't rename the domain. Just Say No. There is no need. Sent from my Windows Phone -- *From: *David Mazzaccaro *Sent: *2/1/2013 9:50 PM *To: *NT System Admin Issues *Subject: *RE: Rename 2003 domain Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate…. But it doesn’t go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use “company.com” on in the internet. So if we never use “company.NET” on the outside, why couldn’t/shouldn’t I rename the domain to that? Thx *From:* Webster [mailto:webs...@carlwebster.com webs...@carlwebster.com] *Sent:* Friday, February 01, 2013 12:23 PM *To:* NT System Admin Issues *Subject:* RE: Rename 2003 domain Go to the archives and read the “SSL and the new no internal names ruling” thread. I think you are going in the wrong direction. Thanks Webster *From:* David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.comdavid.mazzacc...@hudsonmobility.com] *Sent:* Friday, February 01, 2013 9:48 AM *To:* NT System Admin Issues *Subject:* Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name “company.town.main”* *** It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So… I will be renaming the domain to “company.net” this weekend. I have already
RE: Rename 2003 domain
Go to the archives and read the SSL and the new no internal names ruling thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name company.town.main It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So... I will be renaming the domain to company.net this weekend. I have already registered the company.net name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: XDR-fixup Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%ifile:///\\%25%25i -f -r -t 05 My question is... has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha's that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: Rename 2003 domain
Thx I Just read through that thread. One comment was that you never need to register an internal name on a certificate But it doesn't go into detail as to why. The other bigger headache (which I understand) is to NOT use an internal name that will also be used externally. We only use company.com on in the internet. So if we never use company.NET on the outside, why couldn't/shouldn't I rename the domain to that? Thx From: Webster [mailto:webs...@carlwebster.com] Sent: Friday, February 01, 2013 12:23 PM To: NT System Admin Issues Subject: RE: Rename 2003 domain Go to the archives and read the SSL and the new no internal names ruling thread. I think you are going in the wrong direction. Thanks Webster From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] Sent: Friday, February 01, 2013 9:48 AM To: NT System Admin Issues Subject: Rename 2003 domain I will be upgrading my domain from 2003 to 2008 R2 and Exchange 2003 2010. Apparently E2010 does not like my current domain name company.town.main It wants (needs?) a name that can be registered w/ an internet registrar in order to obtain a certificate. So... I will be renaming the domain to company.net this weekend. I have already registered the company.net name. From what I have read, it is fairly (?) straightforward: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx Then there are specific Exchange changes: XDR-fixup Then it seems EVERY computer needs to reboot twice for them to see the new domain. I do have a script for this and a txt file w/ all the machines in it: for /f %%i in (machines.txt) do shutdown -m \\%%i file:///\\%25%25i -f -r -t 05 My question is... has anyone here successfully renamed a 2003 domain (especially w/ Exchange 2003 in it)? Care to share your experience and any gotcha's that came up? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin . ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
