Yes SBS 2008 allows for coexistence with another SBS DC. I believe its actually 30 days.
SBS 2003 to 2008 Std its like 7 days or something before SBS will start rebooting every hour. There are ways to disable that SBS licensing check, but that is a violation of the EULA and I would not recommend doing it unless its causing a major issue with a transition and then only for a limited time. :) Greg Sweers CEO ACTS360.com<http://www.acts360.com/> P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax From: HELP_PC [mailto:[email protected]] Sent: Monday, October 18, 2010 12:22 PM To: NT System Admin Issues Subject: R: SBS2003 Migration Question I would like to know if this 7 days cohexistence is valid also for sbs2003 and sbs 2008 GuidoElia HELPPC ________________________________ Da: Jonathan Link [mailto:[email protected]] Inviato: lunedì 18 ottobre 2010 17.58 A: NT System Admin Issues Oggetto: Re: SBS2003 Migration Question +1 I could do the research, most of us are quite capable. Having everything laid out, along with some common pitfalls was extremely helpful. It's a small price to pay to condense hours of research for something that is rarely done, but it so very important that it be done right. MBS put a blog post about this process sometime back, too. http://theessentialexchange.com/blogs/michael/archive/2008/05/18/sbs-2003-hardware-migration-upgrade.aspx On Mon, Oct 18, 2010 at 11:46 AM, <[email protected]<mailto:[email protected]>> wrote: Amen to that. SBSMigration.com was well worth every penny for our migrations from SBS 2003, to Standard servers and SBS 2003 to SBS 2008. Greg Sweers CEO ACTS360.com P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax -----Original Message----- From: John Cook [mailto:[email protected]<mailto:[email protected]>] Sent: Monday, October 18, 2010 11:33 AM To: NT System Admin Issues Subject: RE: SBS2003 Migration Question Hopefully he already read this, http://www.microsoft.com/downloads/en/details.aspx?FamilyID=52b7ea63-78af-4a96-811e-284f5c1de13b&displaylang=en . I can only say that my small contribution to sbsmigration.com<http://sbsmigration.com/> was money well spent when I did it. John W. Cook System Administrator Partnership For Strong Families 315 SE 2nd Ave Gainesville, Fl 32601 Cell (352) 215-6944 MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4 -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] Sent: Monday, October 18, 2010 11:25 AM To: NT System Admin Issues Subject: RE: SBS2003 Migration Question Only when used appropriately, or it will be your deadliest enemy.. :) 1. Make sure you have all your mailboxes and public folders replicated off. 2. Make sure you have a active GC other than your old SBS. You should have moved all FSMO roles before number 3. 3. Dcpromo old server, it will tell you if there is something left on it that needs to be moved off. 4. Clean up any old records, DNS, WINS, Old computer account. **Note, until computers with Outlook configured talk to the old exchange box and get the referral to the new one they will point to the old one if you take it offline too quickly.** Once they have all changes you can shutdown Exchange, otherwise you will need to edit the profile on the local machines. Greg -----Original Message----- From: John Cook [mailto:[email protected]<mailto:[email protected]>] Sent: Monday, October 18, 2010 8:46 AM To: NT System Admin Issues Subject: RE: SBS2003 Migration Question ADSIEDIT is your friend..... John W. Cook System Administrator Partnership For Strong Families 315 SE 2nd Ave Gainesville, Fl 32601 Cell (352) 215-6944 MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4 -----Original Message----- From: Brian Caisse [mailto:[email protected]<mailto:[email protected]>] Sent: Monday, October 18, 2010 8:27 AM To: NT System Admin Issues Subject: RE: SBS2003 Migration Question The old exchange server is still in the AD. You must remove/decommission the old exchange server. You will also want to DCPROMO the old SBS box also to completely remove it from AD. Brian -----Original Message----- From: Shawn Everett [mailto:[email protected]<mailto:[email protected]>] Sent: Sunday, October 17, 2010 11:28 PM To: NT System Admin Issues Subject: SBS2003 Migration Question Hi Guys, It's rather late and my brain's fried. Hopefully someone can point out what I missed. I have managed to migrate SBS2003 to Windows 2008 Standard Edition w/ Exchange 2010. AD has replicated, the files and permissions are good, Mailboxes all moved, DNS and DHCP looking reasonable. At this point I have not moved the FSMO roles or anything like that. We shut down both the old SBS2K3 server and the new 2008 server and reorganized the server room. I then turned on only the 2008 server. Workstations can log into the domain and show the logon server as the new server. Interestingly Outlook on the workstations will not successfully connect to Exchange on the new server. The server name in Outlook does point to the new server. Shutting down the new server and starting the SBS server and then the 2008 server allows Outlook to work successfully. I suspect I have to transfer a role or something equally basic. Can someone please provide a hint? Thanks Shawn ~ 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 [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. ~ 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 [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. ~ 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 [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> 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 [email protected] with the body: unsubscribe ntsysadmin
