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
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 -
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 -
Conecting to the internet Via a SBS 2003 Windows server
I have 2 macs connected through a 10/100 tbase switch and a SBS 2003 windows server also connected to the switch. The widows server is what accesses the internet. how do i get the macs to pick up the conection???
Hi, and a warm welcome to the forums!
http://www.chicagotech.net/icssetup.htm
http://support.microsoft.com/kb/324286
http://www.ifelix.co.uk/tech/index.html -
Migrate SBS 2003 with AD and Exchange to Windows Server 2012 Standard
We are using SBS 2003 and we have configured Exchange server and AD with DNS and DHCP. Now we are planning to move SBS 2003 to Separate servers like windows server 2012 standard AD with DNS and DHCP and Windows server 2012 Standard with Exchange
2010.
Is it Possible?? we need step by step guide.
Thanks in advance.Hi,
You probably would not find any step by step guide for this kind of migrations. If you are not comfortable with doing such migrations I would recommend to if you need to do it your self do some test migrations. Or otherwise get help by a local IT company
that is familiar with migrations.
But to give you some information, first thing before starting a migration is check the health of your SBS 2003 server / domain. Use tools like dcdiag, netdiag and best practice analyzer. I wrote a blog post about steps to think about before you start this
might help: http://blog.ronnypot.nl/?p=914
When every thing is clean you can start adding the new windows server 2012 machines as member servers to your domain.
Next you can promote one of the servers to additional domain controller on your domain (Keep in mind SBS needs to hold all FSMO roles so moving these is the last step your should do.) Also promoting a windows server 2012 to domain controller has slightly
changed, you need to install the ADDS role and follow the wizard to promote the server to a DC.
With installation of the new DC install DNS allongsite it will automatic replicate settings during confiugration.
DHCP must be installed manual, depending on your scope and settings it might be as easy to create a new scope and disable the old dhcp server.
On the server Exchange needs to be installed, make sure you install and do all pre-requirements. Than install Exchange it will automaticly detect you already have an Exchange organization and is installed as additional server. You can configure all settings
and when everything is configured right you start moving mailboxes.
When everything is moved away from the SBS 2003 server, uninstall exchange, move the FSMO roles to the new DC and after that demote the sbs 2003 server so it is not listed anymore as an additional DC in the domain. Last would be shutdown the server and remove
all records left in AD and DNS.
There is this guide for migrating SBS 2003 to windows server 2008 R2 and Exchange 2010, this might give you some usefull information, not everything will be the same but it is a good start:
http://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/
Regards Ronny
Visit my Blog or follow me on
Twitter -
SBS 2003 - Usage Server Report
Hello,
We use the
SBS 2003
server (+Exchange server
2003). We use Outlook Web Access.
Unfortunately in the "usage
report
server"
does not show the
statistics
about the activity of
OWA.
Could you
advise
How to
solve this problem.
Thank you in advance
J.ZabranskyHi J.Zabransky,
Just addition. Please re-run the Monitoring Configuration Wizard to enable and configure report preferences
or other monitoring features again. Then monitor the result.
Please also refer to following articles and check if can help you.
Understanding the server usage
report
Using the Monitoring Configuration
Wizard
If any update, please feel free to let us know.
Hope this helps.
Best regards,
Justin Gu -
Windows SBS 2003 to Server 2012 Essentials R2
I am tasked with upgrading from an existing SBS 2003 server to 2012 R2 Essentials. Currently the 2012 box is on the network, fresh install but I'm encountering issues from there. I joined it to the domain and now when it boots up it goes through the process
of configuring it to the domain. However, it simply stops with the error "Configuration Encountered Some Issues". Could someone provide some guidance? Thanks!
The only error I can find related to it is:
Log Name: Microsoft-Windows-ServerEssentials-Deployment/Deploy
Source: Microsoft-Windows-ServerEssentials-Deployment
Date: 2/8/2015 10:34:21 PM
Event ID: 130
Task Category: None
Level: Error
Keywords:
User: SNL\halo
Computer: Server2012.snl.local
Description:
Unexpected error occured: System.Management.Automation.CmdletInvocationException: Value cannot be null.
Parameter name: container ---> System.ArgumentNullException: Value cannot be null.
Parameter name: container
at Microsoft.WindowsServer.Essentials.ActiveDirectory.DirectoryEntryExtensions.GetNewChildName(DirectoryEntry container, String preferredName)
at Microsoft.WindowsServer.Essentials.ActiveDirectory.WellKnownStandaloneMsa.Initialize(Domain domain, DirectoryEntry master, Guid wkguid, String preferredName, DirectoryEntry& entry, String& connectedServer)
at Microsoft.WindowsServer.Essentials.ServerSetup.ServerSetupMsaHelper.InitializeServiceAccount()
at Microsoft.WindowsServer.Essentials.ServerSetup.ServerSetupMsaHelper.UseServiceAccount(NetworkCredential credential)
at Microsoft.WindowsServerSolutions.Setup.Commands.InitialConfigurationHelper.StartInitialConfiguration(PSCredential credential, Dictionary`2 data)
at Microsoft.WindowsServerSolutions.Setup.Commands.InvokeEssentialsConfigureServiceCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Windows.ServerManager.ServerEssentials.Plugin.RemotePSHelper.InvokeRoleConfigurationCommand(String command, IDictionary`2 parameters, Func`1 isCancellationRequested, Action`1 onProgress)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-ServerEssentials-Deployment" Guid="{AD9FC988-EB6F-43AF-9429-7BCDB78A7663}" />
<EventID>130</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-02-09T03:34:21.429892000Z" />
<EventRecordID>180</EventRecordID>
<Correlation ActivityID="{E85BC2B0-4415-0000-D0C2-5BE81544D001}" />
<Execution ProcessID="3140" ThreadID="2628" />
<Channel>Microsoft-Windows-ServerEssentials-Deployment/Deploy</Channel>
<Computer>Server2012.snl.local</Computer>
<Security UserID="S-1-5-21-3716708206-3900771979-3496404321-1138" />
</System>
<EventData>
<Data Name="Message">System.Management.Automation.CmdletInvocationException: Value cannot be null.
Parameter name: container ---> System.ArgumentNullException: Value cannot be null.
Parameter name: container
at Microsoft.WindowsServer.Essentials.ActiveDirectory.DirectoryEntryExtensions.GetNewChildName(DirectoryEntry container, String preferredName)
at Microsoft.WindowsServer.Essentials.ActiveDirectory.WellKnownStandaloneMsa.Initialize(Domain domain, DirectoryEntry master, Guid wkguid, String preferredName, DirectoryEntry& entry, String& connectedServer)
at Microsoft.WindowsServer.Essentials.ServerSetup.ServerSetupMsaHelper.InitializeServiceAccount()
at Microsoft.WindowsServer.Essentials.ServerSetup.ServerSetupMsaHelper.UseServiceAccount(NetworkCredential credential)
at Microsoft.WindowsServerSolutions.Setup.Commands.InitialConfigurationHelper.StartInitialConfiguration(PSCredential credential, Dictionary`2 data)
at Microsoft.WindowsServerSolutions.Setup.Commands.InvokeEssentialsConfigureServiceCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Windows.ServerManager.ServerEssentials.Plugin.RemotePSHelper.InvokeRoleConfigurationCommand(String command, IDictionary`2 parameters, Func`1 isCancellationRequested, Action`1 onProgress)</Data>
</EventData>
</Event>Hi Kieran S,
As Robert mentioned, did you refer to any migration guide?
Migrate from Previous Versions to Windows Server 2012 R2 Essentials or Windows Server Essentials Experience
Windows Server 2012 R2 Essentials Migration – Keys to Success
-->it simply stops with the error "Configuration Encountered Some Issues".
Please refer to Paul's suggestion and check if help you to solve this configuration issue. In addition, you can also refer to following KB.
The Post-Deployment Configuration task may fail after you install the Windows Server Essentials Experience role on Windows Server 2012 R2
If any update, please feel free to let us know.
Best regards,
Justin Gu
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]
Those two links were very helpful! Way better than the one I was referencing. I ended up having to manually do a adprep /forestprep before the wizard would work. All is well now, thanks! -
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:\> -
Migrating DC's from Server 2003 to Server 2008 Enterprise R2
I am in the process of testing a migration of our DC's to 2008 R2.
I've read countless articles, step by steps, etc, but am still having trouble deciding the best way to figure this thing out. Hoping that someone can give me some pointers on what might be the best way to do this. It should be fairly straightforward but
I am just unsure of how the fact that the two DC's being on different networks & the DFS will play in to things.
I currently have
(1) PDC residing in a colo (172.16.36.x) Server 2003
(1) Mail server residing in a colo (172.16.36.x) Server 2008
(1) DC residing in our office (172.16.35.x) Server 2003
These 2 different networks are connected by VPN from our office to the colo.
The DC in the office is running DHCP and DNS. It also acts as the File Server. The data is then being replicated using DFS from the office DC to the colo PDC.
We have purchased 2 new servers (physical) to replace the DC and PDC and also am installing Server 2008 R2.
From what I've gathered, I should join these new machines to the domain and begin migrating.
Step 1: Install Active Directory on new Servers, Install/Migrate DNS?
Step 2: Transfer Roles (Looking for recommendation as to which DC acts for which Role also, or should the PDC hold all roles?)
Step 3: Migrate files/shares and set up DFSR?
If anyone can offer some advice on how to make this as simple as possible I would greatly appreciate it!Thanks for the link. I've been able to successfully migrate almost everything over, just had a few questions about DFSR.
This is the scenario:
Server A (old file server, located in office)
Server B (old file server, located in colo)
Server C (new file server, located in office)
Sever D (new file server, located in office)
I have 2 servers currently. Both running Server 2003 (DFS) acting as file servers. Server A is the preferred connection when using DFS, so typically any changes from users will be made on Server A and then replicated to Server B. I've tested the File
Server Migration Toolkit to migrate files/shares over from server B to Server D, it seems to work fine. Now, I am not sure what the best way to migrate everything would be.
This was my thought process but I am not certain this is the best way/or will work as intended.
Use FSMT to copy all shares from Server A to Server C.
Plan for short downtime to copy all open files from Server A to Server C.
Map users to shares on Server C.
Begin replication from Server C to Server D. When complete map users to DFSR link.
Then take Server A and B offline.
Something I wasn't sure about is maybe using FMST to migrate things from Server B to Server D. Would it then compare to Server C through DFSR or does this replication have to occur "naturally"?
Something else I am a little confused about is when does DFSR start being used? Do the old servers have to be offline first? -
Using Mac Mail with SBS 2008 + Exchange 2007
Hi,
I'm having a nightmare trying to connect my Mac Mail to our mail server. We just got a brand new SBS 2008 server put in our office, but my Mac Mail doesn't want to connect.
Every time I try, it does show the Certificate, and when I click accept it trys to connect and gives this eror:
"The Exchange Server "myserver.local" doesn't have the minimum required version installed. To use Mail with Exchange, the server must be running Update Rollup 4 for Exchange Server 2007 Service Pack 1 or later. Contact your server administrator."
Obviously the myserver bit isn't the actual server, I just don't want to tell the world our server name.
The server has the required update, it actually has Update Rollup 10 installed as of today.
Any ideas?I think any poster who replys to their own post with something like, "Actually nevermind, I got it working." and leaves it at that despite requests for help, should be banned from ever posting on or visiting any forum on the internet for the rest of their life.
NoahG - you came here looking for answers, hoping and expecting the community to aid you, but can't be arsed to help out others once you found your own solution. You sir are a leach. -
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,
VoonThank 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. :) -
Need NL setupdisc Windows SBS 2003 NL to deinstall Exchange and Demote server
Hi,
To finally demote and phase out a good old Windows 2003 SBS server, we need to uninstall Exchange 2003 first. For deinstallation the deinstallation proces needs the second (2) Windows Small Business 2003 setup CD to complete this
step.
Problem is that we don't have the original CD's. Because it's an Dutch Windows version, do I need the Dutch CD also? Without the CD i can't deinstall Exchange 2003. Maybe CD number 2 can be downloaded from the internet? Old Trial maybe? Any help would
be great!Hi
Best would be to find a reseller in your area to help you out with disks. i had the same problem as well and they came to my rescue.
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment
Hi,
I'm trying to resolve an issue. We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010. We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
off this server and onto the Exchange 2010 environment.
The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010). The TO address is in the format of [email protected] Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
email, because one of our send connectors has, as address space, *.domain.corp. However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
also is an SMTP server. I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
the mail, processes it and then saves it to a file somewhere.
We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server. Any help troubleshooting this issue is appreciated.The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server. You
should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." -
SBS 2003 to Server 2013 migration - How many virtual Servers?
Hi
I need to replace our SBS2003 - we are about 10 users. We use it for:
AD
File/Print
Exchange
SQL
WSUS
Subversion
TrendMicro WFBS
Since there is no current follow up product I feel like I need to setup:
Server 2012 R2
Exchange 2013
SQL Server 2012 Express
I found inconsistent information on how many virtual servers I will need. Is it correct that in contrast to SBS I must have multiple (virtual) servers?
What is best practice for this scenario (# of VM's, "what" goes best with "what", sizes ..)
Thanks a lot for your help .. I have a very good knowledge about the SBS2003 but unfortunately not about the later Standard Server Versions.Well.. best practice would suggest,
1 VM - DC
1 VM - Exchange
1 VM - SQL
Reality though, suggests they may not be required.
What do you 'need'?, is a better question.
Can you move to hosted exchange?
You can certainly use the Hosted Trend Micro AV product which removes the requirement to run a console on your server.
Perhaps 2 VMs would be sufficient a DC, and a second to host your applications and WSUS.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+ -
Cannot get mail the connection to the server failed exchange 2007
We are unable to use activsync externally but we are able internally. We have ran the testexchangeconnectivity and activesync passed. It does fail on the certificate name validation but the dns and port 443 passes.
I'd ask the experts over here.
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrmobilitylegacy&filter=alltypes&sort=lastpostdesc
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Maybe you are looking for
-
How do you update programs in Adobe Creative Cloud?
I understand that the following applications are now available: Lightroom 5.4 Adobe Raw 8.4 Premiere Pro 7.22 However, if I go to any application and to to /Windows/Updates, I get the message: "Your applications are all up-to-date as checked less tha
-
How can I get old Backups from iCloud?
I used to have two devices with the same iCloud account. One of the devices broke, and it was reseted to the original, so I lost all my notes. Then the notes on the iCloud backup disappeared too. How can I get them back? I used to have really importa
-
How to define a description of a DD
There is only ANI displayed in a windows of application We need also displayed the description of account so I add a description to ANI in a windows of application but the description does not display anything but other DD,for example CO,it's descrip
-
It I have to create a pdf from word 2013 (it's a normal a5 book) and i'm on win 7, acrobat xi; when I print it as pdf, the footnotes (which are set by default as beginning from 1 at each new page) in some pages become continous footnotes (they begin
-
FindByPrimaryKeys with multiple primary keys
Hi, I have a table which has a primary key over 2 fields. I have learned that in this case, I must leave out the <primkey-field> tag from my ejb-jar.xml. In my Entity Bean's Home interface, do I still need to declare a findByPrimaryKey finder method