Migration from SBS 2003 to Server 2008

Couple things. First, I wouldn't bother with 2008 at this point. Here's a pretty handy guide for 2012R2.
http://community.spiceworks.com/how_to/57636-migrate-active-directory-from-server-2003-to-server-201...
Second, I'd switch them over to hosted Exchange.
Did you spec your server already?

Hi guys,Very new to dealing with servers too much so please excuse any lack of info/dumb questions!I have been tasked to do a server migration for a small business. The details I know thus far (more to follow soon) are:There is currently only one server. It is running SBS 2003. It functions as a domain controller, and provides AD, DNS, exchange, DHCP and file sharing services. It is a physical server (Dell I believe). They want to move to another physical server running Windows Server 2008.There are around 15 users/terminals.There is a VLAN set up, not sure how yet. The VLAN needs to 'have a strong connection because heavy architect software needs to be used'Here is the plan of action I have so far:Ensure licenses for win server and exchange are bought.Install OS on new server, install all updates, service packs etc.Configure AD...
This topic first appeared in the Spiceworks Community

Similar Messages

Active Directory not replicating from SBS 2003 to Server 2008 R2 Standard

I have an old SBS 2003 server and am migrating to a 2008 R2 server. I followed this guide:
http://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/
I followed the guide (except the exchange stuff, because they are moving from exchange to Google apps for business) and everything went fine.
I removed the sbs from Domain controller status (dcpromo'ed it out) and everything seemed to go fine. I haven't turned off the old server yet, because they are still using it for a couple of other unrelated applications.
After I did this I added new computers to active directory, but they only showed up on the active directory on the old sbs (I think something went wrong when I too the old sbs out of domain controller status).
I ran dcdiag on the new server and this is the result:
  Time Generated: 01/10/2014   14:57:56
            Event String:
            The SiSRaid4 service failed to start due to the following error:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:57:56
            Event String:
            The stexstor service failed to start due to the following error:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:57:56
            Event String:
            The vhdmp service failed to start due to the following error:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:57:56
            Event String:
            The vsmraid service failed to start due to the following error:
         A warning event occurred. EventID: 0x8000001D
            Time Generated: 01/10/2014   14:58:00
            Event String:
            The Key Distribution Center (KDC) cannot find a suitable certificate
to use for smart card logons, or the KDC certificate could not be verified. Sma
rt card logon may not function correctly if this problem is not resolved. To cor
rect this problem, either verify the existing KDC certificate using certutil.exe
or enroll for a new KDC certificate.
         An error event occurred. EventID: 0x0000164A
            Time Generated: 01/10/2014   14:58:20
            Event String:
            The Netlogon service could not create server share C:\Windows\SYSVOL
\sysvol\PIIKANIPW.local\SCRIPTS. The following error occurred:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:58:21
            Event String:
            The Qntm3520 service failed to start due to the following error:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   14:58:36
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         A warning event occurred. EventID: 0x00002724
            Time Generated: 01/10/2014   14:58:40
            Event String:
            This computer has at least one dynamically assigned IPv6 address.For
reliable DHCPv6 server operation, you should use only static IPv6 addresses.
         A warning event occurred. EventID: 0x800013B8
            Time Generated: 01/10/2014   14:58:49
            Event String:
            The application '/tmsWebAgent' belonging to site '1' has an invalid
AppPoolId 'Classic .NET AppPool' set. Therefore, the application will be ignore
d.
         A warning event occurred. EventID: 0x80003BC4
            Time Generated: 01/10/2014   15:01:53
            Event String:
            SSL Certificate Settings deleted for Port : 0.0.0.0:50106 .
         A warning event occurred. EventID: 0x80003BC5
            Time Generated: 01/10/2014   15:01:53
            Event String:
            SSL Certificate Settings created by an admin process for Port : 0.0.
0.0:50106 .
         An error event occurred. EventID: 0xC0001B7A
            Time Generated: 01/10/2014   15:01:59
            Event String:
            The TMS Print Agent service terminated unexpectedly. It has done th
is 1 time(s).
         A warning event occurred. EventID: 0x0000000C
            Time Generated: 01/10/2014   15:02:00
            Event String:
            Time Provider NtpClient: This machine is configured to use the domai
n hierarchy to determine its time source, but it is the AD PDC emulator for the
domain at the root of the forest, so there is no machine above it in the domain
hierarchy to use as a time source. It is recommended that you either configure a
reliable time service in the root domain, or manually configure the AD PDC to s
ynchronize with an external time source. Otherwise, this machine will function a
s the authoritative time source in the domain hierarchy. If an external time sou
rce is not configured or used for this computer, you may choose to disable the N
tpClient.
         An error event occurred. EventID: 0x0000165B
            Time Generated: 01/10/2014   15:02:34
            Event String:
            The session setup from computer 'PK-PC1' failed because the se
curity database does not contain a trust account 'PK-PC1$' referenced by t
he specified computer.
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:03:37
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         A warning event occurred. EventID: 0x000727AA
            Time Generated: 01/10/2014   15:04:01
            Event String:
            The WinRM service failed to create the following SPNs: WSMAN/PKDC01.
PIIKANIPW.local; WSMAN/PKDC01.
         A warning event occurred. EventID: 0x80003BC4
            Time Generated: 01/10/2014   15:06:54
            Event String:
            SSL Certificate Settings deleted for Port : 0.0.0.0:50106 .
         A warning event occurred. EventID: 0x80003BC5
            Time Generated: 01/10/2014   15:06:54
            Event String:
            SSL Certificate Settings created by an admin process for Port : 0.0.
0.0:50106 .
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:08:37
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x000016AD
            Time Generated: 01/10/2014   15:13:21
            Event String:
            The session setup from the computer PK-PC1 failed to authentic
ate. The following error occurred:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:13:38
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:18:39
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:20:28
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000457
            Time Generated: 01/10/2014   15:20:33
            Event String:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:23:39
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:28:40
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:33:41
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:38:41
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved.
         ......................... PKDC01 failed test SystemLog
      Starting test: VerifyReferences
         ......................... PKDC01 passed test VerifyReferences
   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation
   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test
         CrossRefValidation
   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
   Running partition tests on : PIIKANIPW
      Starting test: CheckSDRefDom
         ......................... PIIKANIPW passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... PIIKANIPW passed test CrossRefValidation
   Running enterprise tests on : PIIKANIPW.local
      Starting test: LocatorCheck
         ......................... PIIKANIPW.local passed test LocatorCheck
      Starting test: Intersite
         ......................... PIIKANIPW.local passed test Intersite
I also noticed that the SYSvol share on the new server is empty and the NETLOGON share doesn't exist.
Please help! Thanks.

Hi,
Do you currently have any relevant errors in your System or Application logs?
Seems like the replication is not successfully.
An SBS server shouldn't shut down upon detecting the existence of another DC as that's a fully supported scenario.
Regards.
Vivian Wang

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 2003 to Server 2008/Exchange 2007

We are in the process of moving our location and are in need of moving
from SBS to something with more CALs. I want to make this as seemless
as possible for the end-users.
We are currently on SBS 2003.
My plan:
Purchase new 64 bit server with Server 2008 and Exchange 2007.
Add new server to existing domain.
Move/migrate exchange from SBS to new server.
Make sure the user info and and Group profiles move to the new server
(not sure how to do that)
Remove the SBS, and promote the new 2008 to DC.
Possibly rename the 2008 to the same name and IP as the old SBS (so
outlook users do not have to change anything)
Would that be the correct route? If so, what am I missing? (Looks
easy on paper)
Thanks,
Mike

hi
here is a lead
Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
requires that servers have the PowerShell management scripting environment and the
.NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
/domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
schmmgmt.dll
You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
you to make the new server the operations master for the FSMO role we’ve just transferred.
Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
is on the new server.
The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
mailboxes it’s worth writing a PowerShell script to handle the move for you.
Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
format report you can use for further analysis.
We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

Problems Migrating from VS 2003 and CR 2008 to VS 2008

I am in process of upgrading from VS 2003 to VS 2008. At same time u2013 moving from Windows Xp to Windows 7. I was using CR 2008 on the XP and also installed it on Win 7. Now seems I have no support or SDK for VS 2008. Even if I add a new Cr object u2013 the screen us blank.
Any and all assistance would be greatly appreciated.
What do I need to do to get this to work u2013 and be able to safely distribute the resulting project?
Would upgrading to SAP CR 2011 work coupled with downloading the SDK for VS 2010? Or Reinstalling VS 2008?
Thank you
JimH

Hi Jim,
CR for VS 2010 will not work in VS 2008 and CR 2011 does not have an SDK install.
If you have Installed CR 2008 before VS 2008 it won't be integrated into VS. Do a repair install of VS 2008 and that should fix VS, assuming CR 2008 is installed and it's not a CR 2008 Basic, must be higher to get the SDK to install and work. Go into Add/Remove Programs and select CR 2008 and change, use the Custom Option and you should see the option to add .NET. Sorry I don't recall the exact wordage, it's been a while since I installed it.
And be sure to get the latest Service Packs for VS and CR 2008 SP 4. You can get them form the [download page|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/bobj_download/main.htm]
Then check your references, they should be 12.x.x.xxxx and remove the 9.x from your project first if they are there still also. VS usually asks if you want to upgrade so I suspect a repair on CR and then possibly a repair in VS 2008 should fix the problem.
Download page also has the Redist Packages to deploy your app and CR runtime also.
Don

Migration from SBS 2003

We will be replacing our SBS2003 server with new (very beefy) hardware. We will use Windows 2012R2 as DC and ultimately Exchange 2013 (after installing 2010 first). Even though not recommended, we will install Exchange on the DC, as we have a tight budget
and won't require DAG. We have less than 15 users in AD & we plan to change the server name, so we can recreate the AD from scratch, so we realize this is not a true "migration".
If we change the server name on the new server, does this affect the import of Exchange mailboxes into 2010 as long as the usernames & email addresses are exactly the same?
Anything else to be aware of if changing the server name with regards to Exchange?
Thank you!

Hello,
I think you misunderstood my post. We are installing on new hardware and the old server will be decommissioned. On the new server we want to change the name to something else, and change the domain name. We then want to ultimately get mail into
Exchange 2013. Since it is not a migration, not sure if we need to first go to Exchange 2010. How best to do this if not doing a migration? Thank you.

Migrate from sharepont 2010/ SQL Server 2008 R2 to Sharepoint foundation 2013 / SQL Server 2008 R2 SP1 single server

Whenever I upgrade database from sharepoint foundation 2010 to 2013 using powershell ( stsadm.exe -o addcontentdb -url http://.....) I get this error when i try to navigate in Sharepoint Central administration
Help (new window) Go back to site Error Error
core.js
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 194f2b9c-628b-a018-f40a-c1b1772f2763
Date and Time: 7/3/2013 12:22:50 AM
Go back to site Go back to site
ULS viewer from log shows
System.ArgumentException: core.js
at Microsoft.SharePoint.WebControls.ScriptLink.AssertLocalizableCompatibility(String strFile, Boolean localizable)
at ASP._admin_admin_master.__BuildControl__control15()
at ASP._admin_admin_master.__BuildControl__control2()
at ASP._admin_admin_master.__BuildControlSPHtmlTag()
at ASP._admin_admin_master.__BuildControlTree(_admin_admin_master __ctrl)
at System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection)
at System.Web.UI.Page.ApplyMasterPage()
at System.Web.UI.Page.PerformPreInit()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Any help would be appreciated

I have got the same error when using 2010 compatibility mode in my application when displaying a page. Following are error logs I got.
Area : SharePoint Foundation
Category : Web Controls
Level : High
EventID : aikzh
Message : core.js is should be localized in o14, call with attribute
Localizable = "true".
Area : SharePoint Foundation
Category : General
Level : Medium
EventID : 8nca
Message : Application error when access /_layouts/SP_CMN_Message.aspx,
Error=core.js at Microsoft.SharePoint.WebControls.ScriptLink.Asser
tLocalizableCompatibility(String strFile, Boolean localizable)
at ASP._layouts_15_simplev4_master.__BuildControl__control11()
at ASP._layouts_15_simplev4_master.__BuildControl__control3()
at ASP._layouts_15_simplev4_master.__BuildControl__control2()
at ASP._layouts_15_simplev4_master.__BuildControlTree(_layouts_15_si
mplev4_master __ctrl) at
System.Web.UI.MasterPage.CreateMaster(TemplateControl owner,
HttpContext context, VirtualPath masterPageFile, IDictionary
contentTemplateCollection) at
System.Web.UI.Page.ApplyMasterPage() at
System.Web.UI.Page.PerformPreInit() at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBe...
Area : SharePoint Foundation
Category : Runtime
Level : Unexpected
EventID : tkau
Message : System.ArgumentException: core.js at Microsoft.SharePoint.WebCont
rols.ScriptLink.AssertLocalizableCompatibility(String strFile,
Boolean localizable) at
ASP._layouts_15_simplev4_master.__BuildControl__control11() at
ASP._layouts_15_simplev4_master.__BuildControl__control3() at
ASP._layouts_15_simplev4_master.__BuildControl__control2() at AS
P._layouts_15_simplev4_master.__BuildControlTree(_layouts_15_simplev
4_master __ctrl) at
System.Web.UI.MasterPage.CreateMaster(TemplateControl owner,
HttpContext context, VirtualPath masterPageFile, IDictionary
contentTemplateCollection) at
System.Web.UI.Page.ApplyMasterPage() at
System.Web.UI.Page.PerformPreInit() at
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAs...
Area : SharePoint Foundation
Category : General
Level : High
EventID : ajlz0
Message : Getting Error Message for Exception
System.Web.HttpUnhandledException (0x80004005): Exception of type
'System.Web.HttpUnhandledException' was thrown. --->
System.ArgumentException: core.js at Microsoft.SharePoint.WebCon
trols.ScriptLink.AssertLocalizableCompatibility(String strFile,
Boolean localizable) at
ASP._layouts_15_simplev4_master.__BuildControl__control11() at
ASP._layouts_15_simplev4_master.__BuildControl__control3() at
ASP._layouts_15_simplev4_master.__BuildControl__control2() at AS
P._layouts_15_simplev4_master.__BuildControlTree(_layouts_15_simplev
4_master __ctrl) at
System.Web.UI.MasterPage.CreateMaster(TemplateControl owner,
HttpContext context, VirtualPath masterPageFile, IDictionary
contentTemplateCollection) at
System.Web.UI.Page.ApplyMasterPage()...
Area : SharePoint Foundation
Category : General
Level : Monitorable
EventID : aat87
Message : An unexpected error has occurred.
The error appeared while Applying Master Page..
I have managed to fix that removing "15" from MasterPageFile="~/_layouts/15/simple.master", so the path is
MasterPageFile="~/_layouts/simple.master".
Otherwise, it could be fixed changing attribute "Localizable" to true in <SharePoint:ScriptLink language="javascript" name="core.js" OnDemand="true" EnableCustomActions="false" Localizable="false"
runat="server" /> in simplev4.master MasterPage, however this way is not desirable.
hope that could help..

OS Migrations from Winwows 2003 to 2008 Server

Hello Experts,
I wanted to know if we can Migrate our OS From windows 2003 to Windows 2008 without System copy/Database Refresh.
Here is what we have currently installed in Windows 2003 Server
OS: Windows 2003 Server
SID: ECP
Database Oracle: 10g
SAP: ECC 6.0
Cluster: MSCS
SAN: NetApp Storage, with Snapshot from snapdrive technology
Local Drive:
C - Windows 2003 Related files
D - SAP and Oracle Executable files
Shared Drive:
E Drives - Where SAP DATAFILE resides (sapdata1...n)
F Drives - Oracle logs (mirrorlogs, origilog, sapbackup, oraarch, etc..)
S Drives - Message Server relelated files including Kernel/Global/Profile Directories
Here is our plan to migrate to windows 2008 server.
While ECC - Production running, we decided to build SAP on 2 different separate hardware with same specs, on Windows 2008 with MSCS. Then install the fresh NetWeaver/ECC system with SAME SID and build the initial Microsoft clustering for Oracle and SAP like as we did on the windows 2003 Server. Make it looks like Windows 2003 ECP except the OS from SAP and Oracle perspective.
Here is the plan.
Since it is the
- same System ID (SID)
- E, F drives are shared
With NetApp Snapdrive technology, we have an options, disconnect the E and F drive, and connect the drives on the Windows 2008 R1 New Server.
We will also copy the all the Global directory files from old server (Windows 2003) to Windows 2008 (Joblog, spool logs, etc)
Question 1:
Now my question would be, is his will be an good practice option to migrate our OS from 2003 to 2008 windows knowing the technology in hands?
Question 2:
When we install a Fresh SAP system using SAPinst, do SAP Sapinst place any Windows related settings/config automatically into the database?
Question 3:
am I missing any other key facts?
Any advice would be much appreciated.
Thanks In Advance
Kumar

You can do that approach but keep in mind that
- you need to install Oracle 10.2.0.4 directly using a different DVD (Note 1303262 - Oracle on Windows Server 2008). If the source system is still on 10.2.0.2 the procedure is not going to work
- after you switch the disks from old to new all permissions and windows ACLs are gone. Windows stores ACLs as GUIDs, not as names so you will need to replace the old with new ones on the disks you present to the new server. This is also true for other files (joblogs etc.)
- the SAP kernel uses OPS$ to connect to the database, I'd delete and recreate the user after the database is mounted and open.
Markus

Moving to Exchange Online from SBS 2003/Exchange 2003 using PST files instead of cut over migration?

I have a friend who runs a small company with approximately 10 users. They are currently using Small Business Server 2003 and are using Exchange 2003 to a limited degree. They are using POP accounts with a hosting company for external email and
are using Exchange for internal email and calendar sharing. They have several different versions of Outlook including 2003, 2007, and 2010. Most of the users have two mail accounts configured in Outlook - one Exchange account and one account with a hosting
company which provides POP mail boxes. Their MX record currently points to the hosting company not their exchange server. As far as I know, they do not have any static IP addresses or if they do, they are not using them.
I do not believe Outlook versions about 2010 will work with Exchange 2003 and their server is getting older and probably needs an upgrade.
I think they should probably move to Exchange Online since they do not have an IT person on staff.
I've done some research and it looks like the recommended solution is a cut-over migration from Exchange 2003 but it looks like that would require some changes to the existing SBS 2003 / Exchange 2003 server and I'm not sure that we would be comfortable
making those changes.
Would it be possible to sign-up and create the user accounts using Exchange Online and just import the data from the user's PST files?
I tried doing some research it looks like it is possible but one post mentioned needing to modify the mailbox’s legencyDN or they may not be able to reply to old messages. How difficult is that? Can it be done after the messages have been migrated
to Exchange Online.
They only have about 10 users so we are looking for the simplest way to move to Exchange Online, not necessarily the fastest or most efficient.
Any advice would be greatly appreciated.

Hi,
Based on your description, I understand that you want to migrate Exchange 2003 Public Folders to Exchange Online. We can get following messages from this article:
Public Folders in Exchange Online
You can’t migrate public folders directly from Exchange 2003. If you’re running Exchange 2003 in your organization,
you must move all public folder databases and replicas to Exchange 2007 SP3 RU10 or later. No public folder replicas can remain on Exchange 2003.
It seems that can’t migrate on-premise Exchange 2003 public folders to an Office 365.
àOn the client
side we are using Exchange 2007
Did you mean Outlook 2007? Please refer to the following thread and check if can help you.
Migrating Exchange 2003 Public Folders to
Wave 15 Office 365
Hope this helps.
Best regards,
Justin Gu

Migrating Server 2003 to Server 2008 R2

I am in migration hell... the network is a simple one, it has one domain controller running a Windows Server 2003 domain in Windows 2000 Native mode. No other servers but a NAS box are on the network, the rest are workstations. I am migrating it to
a Windows Server 2008 R2 x64 bit server, I used adpre32 to perform the steps on the old server.
Before performing the migration I ran netdiag and dcdiag and came up clean. I ran the adprep steps and everything ran great. I got to the part where I was going to transfer the roles and ntdsutil gives a "connect to server WIN2008SERVERNAME, that's
when I get the binding error "ntdsutil dsbind error 0x5 access is denied".
When I also try to go in via Active Directory Users and Computers (on the original domain controller) and then try to connect to a Domain Controller, I see the new DC but when I go to select it I get "The following domain controller could not be
contacted : WIN2008SERVERNAME.DOMAINNAME.COM Access is denied.
I have run repadmin /showrepl on the original box and it came back as successful. I ran DCDIAG and came up fine. I ran nltest /sc_query:DOMAINNAME.COM which came back as I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN.
Network browsing works fine, all computers logon fine and nslookup runs on both the old server and new one showing the old server as it should until the FSMO roles get transferred.
All of this works fine form the new server, DNS looks good and dcdiag DNS testing came up fine. I'm basically banging my head against a wall at this point.

Here are the NETDIAG results from the source domain controller, notice towards the end where it states that LDAP passed but had fatal errors. This is whats blocking the roles from being transferred. I admit I am lacking the knowledge to repair this
so I appreciate the help.
        KB2898715
        KB2898860
        KB2900986
        KB2901115
        KB2904266
        KB2909210-IE8
        KB2914368
        KB2916036
        KB2922229
        KB2923392
        KB2927811
        KB2929961
        KB2930275
        KB2936068-IE8
        KB921503
        KB923561
        KB925398_WMP64
        KB925876
        KB925902
        KB926122
        KB927891
        KB929123
        KB930178
        KB931768
        KB931784
        KB931836
        KB932168
        KB933360
        KB933566
        KB933566-IE7
        KB933729
        KB933854
        KB935839
        KB935840
        KB935966
        KB936021
        KB936357
        KB936782
        KB937143-IE7
        KB938127-IE7
        KB938464
        KB939653-IE7
        KB941202
        KB941568
        KB941569
        KB941644
        KB941672
        KB941693
        KB942615-IE7
        KB942763
        KB943055
        KB943460
        KB943484
        KB943485
        KB943729
        KB944533-IE7
        KB944653
        KB945553
        KB946026
        KB947864-IE7
        KB948496
        KB948590
        KB948881
        KB949014
        KB950759-IE7
        KB950760
        KB950762
        KB950974
        KB951066
        KB951072-v2
        KB951698
        KB951746
        KB951748
        KB952004
        KB952069
        KB952954
        KB953298
        KB953838-IE7
        KB953839
        KB954155
        KB954211
        KB954550-v5
        KB954600
        KB955069
        KB955759
        KB955839
        KB956390-IE7
        KB956391
        KB956572
        KB956744
        KB956802
        KB956803
        KB956841
        KB956844
        KB957095
        KB957097
        KB958215-IE7
        KB958644
        KB958687
        KB958690
        KB958869
        KB959426
        KB960225
        KB960714-IE7
        KB960715
        KB960803
        KB960859
        KB961063
        KB961260-IE7
        KB961371
        KB961371-v2
        KB961373
        KB961501
        KB963027-IE7
        KB967715
        KB967723
        KB968389
        KB968537
        KB968816
        KB969059
        KB969805
        KB969897-IE7
        KB969897-IE8
        KB969898
        KB969947
        KB970238
        KB970430
        KB970653-v3
        KB971029
        KB971032
        KB971468
        KB971486
        KB971557
        KB971633
        KB971657
        KB971737
        KB971930-IE8
        KB971961-IE8
        KB972260-IE8
        KB972270
        KB973037
        KB973346
        KB973354
        KB973507
        KB973525
        KB973540
        KB973687
        KB973815
        KB973825
        KB973869
        KB973904
        KB974112
        KB974318
        KB974392
        KB974455-IE8
        KB974571
        KB975025
        KB975467
        KB975558_WM8
        KB975560
        KB975713
        KB976098-v2
        KB976662-IE8
        KB976749-IE8
        KB977165
        KB977290
        KB977816
        KB977914
        KB978037
        KB978207-IE8
        KB978251
        KB978262
        KB978338
        KB978542
        KB978695
        KB978706
        KB979306
        KB979309
        KB979482
        KB979687
        KB979907
        KB980232
        KB982132
        Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
    Adapter : Local Area Connection
        Netcard queries test . . . : Passed
        Host Name. . . . . . . . . : SPNET01
        IP Address . . . . . . . . : 192.168.100.2
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.100.1
        Dns Servers. . . . . . . . : 192.168.100.2
                                     192.168.100.4
        AutoConfiguration results. . . . . . : Passed
        Default gateway test . . . : Passed
        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
            No remote names have been found.
        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{A759140A-13DA-481A-8BCB-47F2A6EB9EAF}
    1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
    PASS - All the DNS entries for DC are registered on DNS server '192.168.100.
2' and other DCs also have some of the names registered.
    PASS - All the DNS entries for DC are registered on DNS server '192.168.100.
4' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{A759140A-13DA-481A-8BCB-47F2A6EB9EAF}
    The redir is bound to 1 NetBt transport.
    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{A759140A-13DA-481A-8BCB-47F2A6EB9EAF}
    The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
    [FATAL] Cannot do NTLM authenticated ldap_bind to 'SPNET08R2.SPNET.com': Inv
alid Credentials.
    [FATAL] Cannot do Negotiate authenticated ldap_bind to 'SPNET08R2.SPNET.com'
: Invalid Credentials.
    [WARNING] Failed to query SPN registration on DC 'SPNET08R2.SPNET.com'.
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
    No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
    Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
C:\>

OS Migration from Windows 2003 cluster to Windows 2008 R2 MSCS

We want to go for windows 2008 R2 server ( 64-Bit) MSCS by migrating from windows 2003 Cluster ( 32- Bit) . We are running on ECC 6.0 and oracle 10.2.0.2 DB.
Is it possible ?
Is it traditional System copy if so how to migrate the cluster ?
Regards

> 2. If the oracle version is 10.2.0.2 then does it will support Windows 2008 R2.
You need at least 10.2.0.4 (you need to install that version with a separate DVD, you can't install with the normal Oracle DVD (10.2.0.1). See
Note 1303262 - Oracle on Windows Server 2008
Be aware of the fact that the normal standard support for 10.2.x is ending at end of july (you'll have to pay an extra maintenance fee if you continue to run that version) - see
Note 1110995 - Extended maintenance for Oracle Version 10.2
So if you now do a system copy to new hardware with a new os anyway, I would upgrade to 11.2.
Markus

Migrating dns from windows 2003 to windows 2008 on workgroup env

Hi, We are planning to migrate primary dns server from win 2003 to win 2008. Both the old and new servers will be in work group. I have found few articles on how to proceed.
1. Configure new dns server 2008 R2 box as a secondary zone and doing a zone transfer for froward & reverse lookups from the primary Server 2003 machine. Then changing the name and IP of the Server 2008 R2 machine to
what the Server 2003 box was (after pulling the Server 2003 box off the network) as well as setting the 2008 R2 box as the primary. Neither of the servers will be connected to a domain at any point during or after this process.
2. Copy registry keys and dns files from old to new server
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server\Zones
Right click on the “Zones” node and choose “Export“. Save the export as a .reg file (e.g. DNS.reg).
Copy the DNS.reg file to the destination server and “Merge“.
Copy the DNS files
Copy the contents of the %SystemRoot%\System32\DNS folder from the source machine to the same folder on the destination machine. I received an permissions error while trying to transfer the “Samples” folder. It is not necessary to transfer the samples.
Set the DNS Load method
Using the Administrative Tools -> DNS MMC snap-in, on the “Advanced” tab, set the “Load zone data on startup:” to “From registry“. This tells the DNS server to load all zone data from the registry.
Then change the ip address and hostname of the new server to match that of the old ones and start dns service.
I was wondering which method would be easy and hassle free as I have like 23 zones to transfer.
Any help would be appreciated.
Thanks,
Lakshmi Soma

I would go with the first method as I always try to avoid making registry changes which might result in strange behaviors.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Migrating DHCP Server From OpenSuse to Windows Server 2008 R2 Standard

Hello,
I'm planning to migrate a DHCP server from OpenSuse to Windows Server 2008.
Is there any procedures for that ,Or should i configure my Windows server 2008 DHCP service again.
Thank you

Hi,
I have done somthing similar in the past. Basically i got exported all the scopes and settings from the linux dhcpd service, then created the scopes in Windows, stop linux dhcp service and start windows one. Use conflict detection setting to leverage any
IPs lease from linux server.
Hope it helps.
Regards,
Calin

Moving from SBS 2003 to Hyper V 2012 R2 VM's

Hi Folks,
Apologies if I have posted on the wrong Forum
I will keep this brief .
My customer currently has an old SBS 2003 standard physical server. They utilize the integrated Exchange 2003 system. It now needs to be changed/upgraded due to lack of hard disk space and incompatibility between Outlook 2013 and exchange 2003 amonst other
thing.
SBS is no longer available but as the company has grown substantially in the last few years SBS would have been unsuitable anyway. The company has about 80 user accounts across 60 Computer systems.
I have decided after much research to replace the old SBS2003 system with one new Physical server running Windows 2012R2 Hyper V as the Host O/S.. I have also setup 2 Gen 1 VM's running Server 2012 standard, (NOT 2012 R2). I have then promoted one of the
VM's to be a domain controller simply by adding Active Directory Domain services role. The othe VM will be used as an exchange 2010 server .. I have the Exchange 2010 SP3 installation lying in wait on the second VM but I havent installed yet as it requires
access to domain accounts.
The new Server has about 1 terabyte of Hard drive space and 32 gig Ram. The DC has been allocated 8 gig of Ram and 500 gig of Hard drive space. The exchange 2010 VM has been allocated 12 gig Ram with 150 gig Hard drive space.
What I need now is a guide on how to get this new server installed on my existing network and removing the existing SBS2003 box.
I know i have to attach the new domain Controller VM to the existing domain and allow active directory account information etc to replicate onto the new DC VM. Apparently this can take a few days. I am unsure however at which point I connect the exchange
server to the old sbs2003 box in order to move the mailboxes.. actually I am not even sure if I ever connect the new exchange VM to the old sbs 2003 box. Would it be better to get the DC replaced first. i.e attach the DC to the existing domain.. let the active
directory info to replicate.. transfer the roles, demote the sbs2003 box?? I am concerned that the old mailboxes on the sbs2003 box will then be irretrievable..
Perhaps someone can clarify the steps in sequence that I need to follow to end up with my DC VM and Exchange 2010 VM with migrated mailboxes installed as replacement for the current sbs 2003 box.
Some other notes: Although i have used 2012 R2 for the hyper V host I have decided that 2012 made better sense for the VM operating systems due to the better compatibility with exchange 2010 in one VM and simply because of online advice on the DC VM.
Thanks in advance

This doesn't really have anything to do with Virtual Server 2005 (this forum, or even Hyper-V).
This is migration from SBS to a regular domain. Look at the SBS forums, or Exchange and AD forums for advice moving from SBS to regular Exchange and 2012 AD.
Maybe here:
http://social.technet.microsoft.com/Forums/exchange/en-US/3fae661d-1c34-4728-96ce-7eaf79af64c3/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2?forum=exchange2010
http://technet.microsoft.com/en-us/library/jj200112.aspx

Migration from Exchange 2003

Hi,
We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
Can Office 2011 connect to Mac mail services? If so, what protocols?
Many thanks,
Ciaran.

We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
What features of Exchange are you using? Push notifications? Calendaring. Sharepoint? Figure out what you want and what you need (and which are two separate lists) and then map that over to what Mac OS X Server, or to what a Mac box with the Kerio Connect package loaded, might provide you.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
That's rather open-ended. It's possible, but there's no single definition of small business mail requirements. Some small businesses can and have, and some might find themselves missing critical features.
Can Office 2011 connect to Mac mail services? If so, what protocols?
iWork does well enough to read and write Office files locally, so I don't have experience with Microsoft Office. The Windows mail clients can certainly access Unix mail servers. As for what connectivity is present within Office, I'm way too rusty with Windows to comment. What used to be the Outlook Express client worked just fine with Unix mail servers. The full-on Office Outlook client was pretty flaky with stuff other than Exchange, but that was some years ago.
Biggest issues with SBS migrations tend to be with shared Address Book, with shared Calendars and with Sharepoint services; if you're heavy users of those features, you might find the Mac OS X Server implementations lacking. Kerio can potentially help here.
Look around the forums for some other folks. This particular SBS migration has been fairly common fodder for discussions.

Migration from SBS 2003 to Server 2008

Similar Messages

Maybe you are looking for