Extend SBS 2008 - 2011 Migration

Yes, I know the SBS party has passed. But, I have a client who purchased it before the end of the year, and we are now doing a migration from SBS 2008 to SBS 2011. However, it is taking longer than 21 days.
I know with SBS 2003, you can suspend SBCore and extend the migration.
Can you do the same with SBS 2008?

Hi,
Any update?
Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.
Best Regards,
Andy Qi
TechNet
Subscriber Support
If you are TechNet
Subscription user and have any feedback on our support quality, please send your feedbackhere.
Andy Qi
TechNet Community Support

Similar Messages

Removing Exchange 2007 from SBS 2008 after Migrating to Office 365 Mid Sized with DirSync and SSO

We have recently completed off a Migration of Exchange 2007 to Office 365 Mid Sized platform.
I now need to decomission the old SBS 2008 server as they have moved to a Windows Server 2012 R2 server setup for DC, File and print and application servers.
I need to know what are the ramifications of removing the Exchange 2007 server from the SBS 2008 server and will this remove the LegacyDN details from AD and cause any issues with internal emails between users using Outlook linked through to Office365.
I understand that after removing Exchange 2007 there will be no friendly GUI to update and maintain proxyAddress, targetAddress and LegacyDN addresses, I am comfortable doing this in ADSI edit or with a script.
Will this remove the x500 addresses relating to the on premise Exchange Orgainisation and just leave behind the x500 addresses for Exchange Labs which I assume is the x500 addresses for the Azure AD intergration for Office365.

Hi ,
Thank you for posting your issue in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

SBS 2008 PREMIUM - Migration to Office 365 (E3)

Hi,
I have two customers running 'Windows Server SBS 2008 Premium' and wondering to migrate their environment to 'Office 365', since this is an old version of Windows cannot run the AD FS tool (as my previous post
https://social.technet.microsoft.com/Forums/exchange/en-US/4b5d7942-f9a6-4138-9ba8-596a35e36754/sbs-2008-microsoft-azure-active-directory-module-for-windows-powershell-is-not-supported-by-your?forum=WindowsAzureAD) they will create a new environment with
Windows Server 2012 R2.
Looking at 'https://www.skykick.com/products/small-business-migrations' isn't clear about Active Directory
migration or sync.
Can someone share thoughts and review if my plan is correct to use this tool?
- install a new server and AD domain;
- install SSL and AD FS tool in a way to integrate it with Office 365 Servers
- migrate computers from old DOMAIN (SBS 2008) to the new one (W2k12)
- use this tool to migrate contents from old infrastructure
Any help is appreciated.
tks,
Renato P

Hi ,
Thank you for posting your issue in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Configurations for WSUS on SBS 2008 & 2011

I came across some issues with configuring WSUS on a SBS server for the first time and had a couple of questions.
1. Will WSUS work if you change any configurations on the SBS server? (ex. Product & GP)
2. Can you configure WSUS the way you want and just use the WSUS console instead of the SBS console update?
3. What would the best approach on re-downloading updates after the WSUS content folder has been deleted without the reset command?

Hi,
>>1. Will WSUS work if you change any configurations on the SBS server? (ex. Product & GP)
Please make sure that the settings of the WSUS are applied to the client properly through Group Policy.
>>2. Can you configure WSUS the way you want and just use the WSUS console instead of the SBS console update?
Yes, for detailed information, please refer to the link below:
https://technet.microsoft.com/en-us/library/hh334984%28v=ws.10%29.aspx
>>3. What would the best approach on re-downloading updates after the WSUS content folder has been deleted without the reset command?
wsusutil reset
For detailed information, please refer to the link below:
https://technet.microsoft.com/en-us/library/cc720466(v=ws.10).aspx
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Problem connecting to MS Exchange 2007 on SBS 2008

I am having problems connecting to Exchange via cfexchangeconnection. Our ColdFusion environment is CF9 Enterprise on Win 2008, and the Exchange host is Win SBS 2008 (which uses IIS7).
After having worked through the documentation and following all procedures outlined at
http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WSc3ff6d0ea77859461172e0811cbec14f31 -7fed.html
plus googling intensively, we have the following method to test the connection
<cfexchangeconnection action="open"
         connection="thisExchangeConnection"
         server="portal.mydomain.com"
         protocol="https"
         formBasedAuthentication="true"
         formBasedAuthenticationURL="https://portal.mydomain.com/owa/auth/owaauth.dll"
         mailboxname="myMailBox"
         username="myUsername"
         password="myPassword" />
<cfdump var="#thisExchangeConnection#">
<cfexchangeconnection action="close"
         connection="thisExchangeConnection" />
The IIS7 implementation in SBS 2008 is quite a lot different to Win 2008, so there are some question marks around some steps in the above documentation. However, we have made sure that:-
1) you can use the credentials above to login via a web browser
2) WebDav is on in IIS
3) there is no IWA and forms based authentication is on
4) certificates are installed correctly on both the CF and Exchange servers
5) the myUsernameaccount has correct permissions in iis/owa/exchange
Despite this, the net result is always
Access to the Exchange server denied.
Ensure that the user name and password are correct.
From research it seems that a lot of people have issues where the underlying problem is actually an Exchange 440 timeout error where the password in the IUSR_<servername> and IWAM_<servername> (IIS/Active Directory) is out of sync.
I was pinning my hopes on the above being the problem but now I find that in SBS 2008 there is no IWAM_<servername> server account.
All this leads me to ask is SBS 2008 actually compatible with the cfexchange tags in CF9? There is nothing in the documentation that I can find that syays that it isn't, but given the amount of time we've spent on what should be straightforward I am wondering if we are on a hiding to nothing. Anyone from Adobe care to comment?
If anyone has managed to get this to work specifically with SBS 2008, or has any advice I'd be grateful to here from you.

Hi,
As said by Sneff , I would also recommend to enable Logging to get more detailed information. Also follow
Configuration of POP/IMAP on SBS 2008 Refer to :
http://blogs.technet.com/b/sbs/archive/2008/09/19/how-to-configure-sbs-2008-to-host-pop3-imap4.aspx
http://blogs.technet.com/b/sbs/archive/2011/08/31/how-to-configure-outlook-for-pop3-imap-and-smtp-connectivity-in-sbs-2008-2011-standard.aspx
As per the error code, you need to follow
http://support.microsoft.com/kb/813514/EN-US
I would also disable AV on both Client machine and TEST , including the Filters of AV.
Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

SBS 2008 to 2011 - Forgot to Remove Exchange

Argh! Following the doc for SBS 2008 to SBS 2011 migration. I guess I lost my place.... Went to demote server, I had to remove Certificate Authority first. The instructions for this were AFTER removing Exchange, so I did the Certificate
stuff, FORGOT about Exchange, and kept going....
Since my 21 days were up, I simply shut off the old server.
IN Exchange, the main mailbox, the Outlook Address Book Offline, Public Folders, etc, are all on the new server. When I run the EMC, it does list the 2nd server.
Since I am out of time, have already removed AD from the source server, how much pain do you think this can cause if we just keep the old server off, and cross our fingers?? How bad would it be to turn on the Source Server, reinstall AD services, THEN
remove Exchange, then AD? Would re-adding AD screw up everything?
Appreciate any comments (except telling me to RTFI, lol. Believe me, I wish I had).

No one? I was hoping some sort of MVP or MS Employee would at least offer an opinion as to how bad this is....

Migrate SBS 2008 with exchange 2007 to office365

Hi, we have a sbs 2008 with exchange 2007 the boss got the idea to move the E-mail to office 365, i have done some research but still have some questions, now i am not an expert on exchange, could some one tell me if this is a straight operation going from
exchange 2007 to office 365, is it supported or do we have to move to exchange 2010 and then to office 365?
Thank you very much in advanced.

Yes, going from Exchange 2007 to Office 365 is supported. You want to run a Migration.
Check out this link for exact instructions on what to do for the migration:
http://help.outlook.com/en-US/140/ms.exch.ecp.emailmigrationwizardexchangelearnmore.aspx
Then, when you are ready to setup Outlook with Office 365, check out this link to make Outlook use the public Autodiscover rather than SBS Autodiscover:
http://www.mcbsys.com/techblog/2011/08/using-office-365-in-an-sbs-2008-environment-take-2/
I just did a cutover migration from SBS 2008 to Office 365 using both these websites and it went off very nicely.
Good luck on your migration.
Oh, and if you only use Office 365 for email, it is $4 a month per user.

SBS 2008 - Essentials 2012 R2 migration

Hi,
We installed Essential R2 ( no more SBS , first bad thing and found no migration tool for R2 ... second bad thing ) , when starting the wizard we were not able to put our domain name in ( already exists .... third bad thing)
So how could we migrate easily from a SBS to a Essentials R2 without starting from scratch ( what was possible between NT & 2000, 2000 & 2003 , 2003 & 2008 and 2008 & 2011 ) ?
Thanks in advance
Regards
Dirk
Dirk

You install the server. You hit cancel at the launch.
You don't need a migration wizard any more. What exactly have you done?
http://blogs.technet.com/b/sbs/archive/2014/02/21/deploying-windows-server-2012-r2-essentials-in-an-existing-active-directory-environment.aspx
Windows Server 2012 R2 Essentials Migration – Keys to Success - The Windows Server Essentials and Small Business Server Blog - Site Home - TechNet Blogs:
http://blogs.technet.com/b/sbs/archive/2014/03/31/windows-server-2012-r2-essentials-migration-keys-to-success.aspx
Unfortunately TechNet subscriptions aren't coming back, sorry folks :-(

How can I edit the way autodiscover.xml behaves in SBS 2008 and 2011?

I have autodiscover working correctly on a few SBS 2008 and SBS 2011 servers. But, its doing its usual misbehaving. When setting up a new Outlook profile, the user enters their email address and password. Autodiscover is successful in creating all
the account settings, but at the end of the wizard a username and password window pops up with the users full email address incorrectly filled in as the username, which is why it didn't work.
This has always been so annoying about SBS. The user then has to be told to delete their email address in the username field, then fill in "domain\username" instead. Only then is the authentication successful.
I've read lots about people adding the external domain UPN Suffix to ADD&T, then manually changing ever users login to domain.com instead of domain.local.   Then you have to mess with the owa authentication settings in exchange to accept the
UPN.   Its all too ridiculous. There must be a simpler way.
I have read about how you can control how the autodiscover.xml behaves, and there are examples of how to do it in this document:
https://docs.google.com/viewer?a=v&q=cache:0jap1FNKgV0J:https://support.quest.com/Shared/Images/SOL51188_Outlook%2520Automatic%2520Account%2520Configuration.doc+&hl=pl&gl=pl&pid=bl&srcid=ADGEESjizUeFf-JYaM7ZdfIgUCKMMXtcCl0Y3pknFbuwd64GNHIEP1K8a_mpg2YIEisP6sz5DzbtVtdW4Pc42PE0Kjd6bz-3vXz0iaQm7FKi0AnwgvFG_41ZAkBLWynaJtf8s8xyi_d2&sig=AHIEtbSie1mEHTn8el4DPquNxrpovwknUQ
The document above shows the settings we need to change. It looks like we can add the local domain using DomainName into the autodiscover.xml and this will stop autodiscover reporting that the full email address is required.  So we
should be able to get autodiscover to populate the username pop-up with with "domain\user" automatically.
OK, so my question is, how on earth do I edit these settings in SBS 2011? I can't find any articles that talk about how to edit autodiscover.
If I could just edit this one setting (that Microsoft should have correctly configured in the first place) autodiscover will work perfectly for all existing users and all future users, without having to do anything.

Just to straighten out a few things;
1) This is NOT a bug, rather by design. Not every active directory has an exchange server in place, and MS is assuming you don't want to give your internal domain name out to people (which is why it doesn't default to domain\username)
2) Going on what I said in 1), this is NOT SBS specific this is the same way with every Active Directory/Exchange install, keep in mind Microsoft did NOT specially design the software for SBS, they just bundled it into a supported configuration in a neat
little package -since the Exchange server we run on SBS is the same Exchange server powering hundreds of hosted email providers -it makes sense why autodiscover doesn't provide the domain\username (imagine what a mess that would be!)
3) I understand it's a little bit time consuming but it can actually be done for all users in a matter of seconds, select all users, right click and go to Properties, you can then choose the UPN Suffix for all users. When a new user gets created one of the
settings in the wizard is the UPN suffix and is easily changeable as long as you notate for the person creating the user to do it. (The problem here is if you're using the SBS Console instead of AD to setup the User in which case that's just an oversight
in design not a bug in the programming)
4) You can most certainly have a powershell script that changes the UPN suffix from A to B, let me know if you're interested I'll dig one up for you. That can be run on a scheduled task and will solve the remaining issues you have :)
I do see you mentioned it in number 3, I must have missed since I didn't re-read the OP before posting the article, however I just tested on several SBS 2011 machines and OWA authentication settings don't have to be changed at all, this worked immediately
for Outlook Anywhere and Outlook Web Access in my lab and two different customer production systems.
-GreenlightTech

SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

Hello,
We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
2010 cannot be installed".
Here is the end of 'ExchangeSetup.log' showing various error messages:
[11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
[11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
[11/29/2014 23:00:07.0522] [2] Unexpected Error
[11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
[11/29/2014 23:00:07.0523] [1] Executing:
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
[11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
[11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
[11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[11/29/2014 23:00:07.0609] [1] [ERROR] The following error was generated when "$error.Clear();
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
" was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
[11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
[11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
[11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
[11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/29/2014 23:00:07.0633] [0] End of Setup
[11/29/2014 23:00:07.0633] [0] **********************************************
[11/29/2014 23:39:03.0429] [0] **********************************************
[11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
[11/29/2014 23:39:03.0435] [0] **********************************************
[11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
[11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
[11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
[11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
[11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
[11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
[11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
[11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
[11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
[11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
[11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
[11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
[11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
[11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
[11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
[11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
[11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
[11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
[11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
[11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
[11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
[11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
[11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
[11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
[11/29/2014 23:39:13.0920] [0] Applying default role selection state
[11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
[11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
[11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
[11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
[11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
[11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
[11/29/2014 23:39:26.0117] [0] End of Setup
[11/29/2014 23:39:26.0117] [0] **********************************************
I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
Thanks,
Voon

Thank you Larry and Al for your replies.
I used the 'official' migration
guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

SBS 2008 - SBS Console and AD errors after migration to new hardware

Hi there,
I'm trying to work out how to fix some of the errors and random behaviour I'm experiencing with the SBS 2008 console and AD related matters since I had to quickly migrate SBS 2008 to new hardware using Windows Server Backup after a failure of the old server.
In my haste to get our email and ftp services back up and running (which use Smartermail and Filezilla respectively instead of Exchange etc) I overlooked the fact that the new server had 3 NICs installed and not one and so restored SBS 2008 and loaded up new
drivers for those and other hardware that had changed (such as the graphics card and mobo. I have since removed the two additional NICs by disabling them on the mobo).
Whilst I got the server up and running again with email and ftp services, even though I currently don't use any AD related stuff directly I have since noted that if I try to say view a list of users that I had previously created via the SBS console, more often
than not it will show no users, and then randomly it will (but when you do see them you can't edit or delete them. I'm aware that I have probably broken a number of golden rules in doing this 'migration' but having a metaphorical gun to my head meant that
I rushed things out of desperation.
Common errors that I experience generally will say things like 'Current security connect is not associated with an Active Directory domain or forest' if I try to list users, or DC not found for domain "xyz.local' etc. I have been searching the net and
trying out some things to fix this but I'm like a dog chasing its tail as I'm not so clued up on server related issues as I am with workstation problems, so if anyone could at least point me in the right direction I would be very grateful. If you require any
info from me (eg diag logs etc) I will be happy to provide them!
Regards,
Dave

Hi Dave,
Based on current situation, please run SBS BPA and fix all that it can find, then monitor the result. For more details, please refer to the following KB.
Windows SBS Best Practices Analyzer (BPA)
Meanwhile, please refer to the following article and repair SBS console.
Repair the Windows SBS 2008 Console
By the way, I noticed that you had got some error messages (such as: “DC not found for domain” and so on). Would you please let me know complete error messages? In addition, when you migrate SBS 2008 to the new hardware, had you done any preparation for
that Source Server? For more details, please refer to the following article.
Migrate Windows Small Business Server 2008 to New Hardware
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Accidently removed a mailbox on the SBS 2008 server during the migration from SBS 2003

I accidently removed a legacy mailbox from the SBS 2008 server while still doing the migration from SBS 2003. I meant to click on the Move Mailbox like the instructions said but clicked on the Remove option, then clicked the 'X' to close the box since
I figured that would cancel what I did however it removed the mailbox from the SBS 2008 list.
Please tell me that I can get it back. It still shows up in the old SBS Exchange System Manager but now when an email is sent, it sends back a no delivery message. It's like the account doesn't exist any more.
Can it be recovered and if so, how?
thanks,
Jeff

Hi Jeff,
Would you please let us know current situation of this issue? Just check if above suggestions can help you.
If any update, please feel free to let us know.
In addition, please also refer to following article and thread, and then check if can help you.
How
to use a Recovery Storage Group in SBS 2008
How
to recover a deleted user and mailbox on SBS 2008
Hope this helps.
Best regards,
Justin Gu

SBS 2008 to Server 2012 R2 Active Directory Migration

Is there a tool that i can use to migrate Active Directory from SBS 2008 to Server 2012 R2?

There is no special tool for your situation. While there is a tool called ADMT that you may see mentioned if you search enough, it isn't really well suited for what you want.
With that said, there is also no *need* for a tool as I've already said. Nor do you need to recreate the users and have mismatched SIDs. You will add the 2012 machine to your existing domain and make it a domain controller. Yes, that means you will have
two DCs (for a time.) This is how larger organizations handle multiple DCs all the time, and they obviously don't go and create the same user on each DC. That is where the domain replication comes in. Your new server will be a DC and will replicate
all of the users *and* SIDs from the existing SBS server.
Then, when you are ready, you decommission the SBS 2008 server gracefully and the new 2012 server becomes your sole DC, but has AD completely intact. It is a tried and true practice, both within and outside of the SBS world, and has been done many many times.

Migrate SBS 2008 to new hardware

We have an SBS 2008 installation and are testing a disaster recovery solution by re-installing in Migration Mode.
Step 5 in the migration document from Microsoft discusses;
Demote and remove the Source Server from the network
We'd like to fully test this and get the backup box up and running before signing it off as a working solution.
Our concern is that, even if we isolate the test machine on a difference subnet from our production LAN, there is some kind of licensing consequence for our running box - via some kind of de-activation signal sent over the net, perhaps - should we continue
through the final steps.
Can anyone confirm or deny whether any kind of de-activation occurs? Perhaps paranoia, but thought best to check since we really can't have our live systems shut down.

Hi,
Before going further, would you please provide more detailed information about your concern? It’s difficult to understand your needs for me with the information you mentioned. For details about
how to migrate SBS 2008 to new hardware, please refer to the following articles.
Migrate Windows Small Business Server 2008 to New Hardware
http://technet.microsoft.com/en-us/library/cc664208(v=ws.10).aspx
Moving SBS to new hardware
http://msmvps.com/blogs/kwsupport/archive/2005/06/18/53958.aspx
Hope it helps.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Migrating PDC role from SBS 2008 to Server 2012

Greetings everyone
Are there any special considerations or steps that need be done when elevating my BDC running Server 2012 from a PDC running SBS 2008? We are wanting to remove the SBS machine entirely as we no longer need it and could possibly be of use to one of our clients
down the road.
Thank You
Additional Info: We have already migrated Exchange to the cloud and is no longer hosted on our SBS server. The only function the SBS server has at the moment is being the PDC.

If you haven't seen it already you'll probably want to check out
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx which describes the entire process, though obviously in your case you don't need to worry about the Exchnage side of things.
The main thing in your case will moving the FSMO roles over to the new server so the old SBS box is no longer required. There's a link to the process in that blog post, though as I understand it when 2012 is the destination the recommended route is to grab
the roles from 2012 rather than give them up from 2008. There's a good step by step guide to the process here
http://www.waronerrors.com/kb/how-to-transfer-fsmo-roles-from-windows-server-2003--2008-to-windows-server-2012.aspx though obviously the main thing to note is that as soon as you move the FSMO roles you have 21 days in which to complete the migration. After
that time the SBS box will automatically restart periodically (I think after an hour from memory).

Extend SBS 2008 - 2011 Migration

Similar Messages

Maybe you are looking for