Ok Gents I bow to your knowledge. Though I will continue to transition any customers SBS2003 server 1st before migrating the roles etc to replacement hardware and seperating of Exchange from the DC.
Graeme On Fri, May 9, 2008 at 1:57 PM, NTSysAdmin <[EMAIL PROTECTED]> wrote: > Yup, that's how they sell it.....they talk el crappo.... > > > > The restrictions are built into the OS, not AD. It also leaves Exchange on > a DC which is not good. > > > > S > > > > *From:* Graeme Carstairs [mailto:[EMAIL PROTECTED] > *Sent:* Friday, May 09, 2008 9:10 AM > > *To:* NT System Admin Issues > *Subject:* Re: Removing SBS2003. > > > > Ken, > > I understand what you are saying, > > I don't believe it is and AD issue but we were informed from MS presales > partner support that any Windows 2003 SBS domain that needs to be changed to > full blown windows and exchange, without any of the SBS restrictions needs > the SBS server transitioned using the transtion pack. > > This removes any licensing and user limits, and also converts your SBS cals > to full blown cals. > > For the cost of the transition pack, it makes sense, rather than going out > and buyin Exchange, WIndows, and all the cals required. > > Graeme > > > > > On Fri, May 9, 2008 at 1:01 PM, Ken Schaefer <[EMAIL PROTECTED]> > wrote: > > If you can get some specific technical details, I'd be really interested to > know what they are. > > > > Active Directory isn't aware of "SBS" or otherwise (there is no such thing > as an Active Directory that thinks it's SBS), so whoever your contacts are > will need to elaborate on what it is they are claiming. > > > > Cheers > > Ken > > > > *From:* Graeme Carstairs [mailto:[EMAIL PROTECTED] > *Sent:* Friday, 9 May 2008 9:46 PM > > > *To:* NT System Admin Issues > *Subject:* Re: Removing SBS2003. > > > > Ken, > > thats interesting as we were told by Microsoft that we would need to > transition the SBS server first, as this would fix the domain to full 2003 > AD type not SBS restricted, and then move to new hardware as if not > transitioned then the domain still thinks it is SBS and you can get unusual > results. > > Graeme > > On Fri, May 9, 2008 at 12:28 PM, Ken Schaefer <[EMAIL PROTECTED]> > wrote: > > This would be recommended if you want to keep the existing SBS server in > the environment. > > > > If you want to transition to alternate machines (e.g. separate Exchange > servers, DCs, WSS boxes, because the existing hardware is due to be > retired), then this isn't really necessary. > > > > Cheers > > Ken > > > > *From:* Graeme Carstairs [mailto:[EMAIL PROTECTED] > *Sent:* Friday, 9 May 2008 5:53 PM > > > *To:* NT System Admin Issues > *Subject:* Re: Removing SBS2003. > > > > Microsoft do an SBS 2003 to windows Transition pack. > > You run it on your SBS 2003 server and it converts it to a full blown > Windows 2003 DC running full Exchange 2003 standard. It also converts your > SBS cals to Windows 2003 and Exchange 2003 cals. > > It is the recommended way to carry out this change. > > It works successfully we have done upwards of 10 transitions, but there > were 2 which were problematic but a free call to PSS resovled the issues. > > This leaves you with a full 2003 functional domain without any of the SBS > restrictions. > > Graeme > > On Fri, May 9, 2008 at 7:20 AM, Ken Schaefer <[EMAIL PROTECTED]> wrote: > > Actually, you can just transfer the roles. > > SBS 2003 will complain, but you get a couple of hours before it starts its > shutdown sequence. > > Just run dcpromo on the SBS 2003 box, and that will remove AD from the > SBS2003 box and references to that server in AD (no need for metadata > cleanup). > > Cheers > Ken > > > -----Original Message----- > > From: Phil Brutsche [mailto:[EMAIL PROTECTED] > > Sent: Friday, 9 May 2008 5:41 AM > > To: NT System Admin Issues > > Subject: Re: Removing SBS2003. > > > > It goes something like that... except that the SBS2003 server won't let > > any other machine hold the FSMO roles. You need to "violently" rip > > SBS2003 out and tell the 2003 DC to seize the roles. > > > > The procedure would go something like this: > > > > 1) Bring up 2003 machine > > 2) Add 2003 machine to SBS2003 domain as an additional domain > > controller > > 3) Let the DCs sync > > 4) Pull the plug on the SBS2003 server > > 5) Tell the 2003 DC to seize the roles > > > > Joe Fox wrote: > > > I guess the subject says it all. I have a SBS2003 server on my > > network, > > > and want to replace it with a 2003 Server. Is it as simple as > > bringing > > > the new 2003 box online, promoting it to domain controller, and then > > > transferring the FSMO roles to it from SBS? > > > > > > -- > > > > Phil Brutsche > > [EMAIL PROTECTED] > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > > > > -- > Carbon credits are a bit like beating someone up on this side of the world > and sponsoring one of those poor starving kids on the other side of the > world to make up for the fact that you're a complete shit at home. > > > > > > > -- > Carbon credits are a bit like beating someone up on this side of the world > and sponsoring one of those poor starving kids on the other side of the > world to make up for the fact that you're a complete shit at home. > > > > > > > -- > Carbon credits are a bit like beating someone up on this side of the world > and sponsoring one of those poor starving kids on the other side of the > world to make up for the fact that you're a complete shit at home. > > -- Carbon credits are a bit like beating someone up on this side of the world and sponsoring one of those poor starving kids on the other side of the world to make up for the fact that you're a complete shit at home. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
