SBS 2003 Exchange pub1.edb daily growth

OK, so this may be normal and I cannot see any problem specifically. However, over the last 6 months or so the store has been slowly growing in size and I cannot tell why. It has been running for several years and was mostly static, but now is growing.
It's still not large, but I am trying to find out why this is happening and not seeing anything. The rate of growth is about 51.25MB per day.

Users do the damnedest things with public folders. I've seen people use them to store backups of their laptop's hard drive, and copies of their PSTs!
If the folders are mail-enabled there may be a message loop if there's a PF assistant rule on one or more of the folders. Or it may just be it's just a folder receiving e-mail. Or someone copying mail from their mailbox to a folder.
--- Rich Matheisen MCSE&I, Exchange MVP

Similar Messages

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

SBS 2003 Exchange Server

I have tried and failed to set this up.
I have had to enable SSL IMAP and SSL SMTP on the server to allow my iPhone 4 to connect.
I can connect using the exchange wizard if I turn off the SSL on the iPhone.
I have an SSL cert on my server from a certificate authority.
I have the required 443 port open to the server (and OWA and outlook via HTTP is working fine).
Not too sure where else to look!
Any advice greatly recieved! Even if it's just a consensus of opinion on who else has actually got this working!
Thanks!

Ok, I appear to have got this to now work.
I run the tests available on this site (using a test account setup on the server). https://www.testexchangeconnectivity.com/
I had an error with the HTTP request not returning an authentication method (even though using SSL).
In my SBS2003 default website I opened the active-sync virtual directory properties and set the authentication type to basic authentication. Even though using SSL, this appears to sort the issue and the iPhone connects in SSL mode.

Server 2003 SBS (with Exchange 2003) migrate to new machine Server 2012 Standard (with Exchange 2013)

This is what I have:
A very outdated machine running a small domain, SBS 2003 and Exchange - this is the ONLY server currently.
This is what my boss ordered:
A Dell R210 II machine with Server 2012 Standard (and I downloaded the trial for Exchange 2013).
He wants the old server completely replaced and gone - with everything moved over (including Exchange) to the new machine. The main reason for the upgrade is that not all users can access email on their machines (Macs, new versions of Outlook, etc.)
I have set up a new standalone server before but never migrated one - and I've found that going from SBS2003/Exchange2003 to Server2012/Exchange2013 is not simple in the least.
I thought I could just set up the new server as a DC on the domain and have everything replicated to it from the source server. Then I could decommission the old server. I have been told that 1) I can't upgrade Exchange 2003 to 2013 and 2) that I shouldn't
put Exchange on a DC. What do you do if you only have the one server?

Hi,
Just additional. Please also refer to following threads and article, then check if can help you.
Migrate
SBS 2003 to Windows Server 2012 Standard
Migration
SBS 2003 to Windows Server 2012 Standard
Transition
from Small Business Server to Standard Windows Server
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

Best way to sync Outlook 2007 calendar with Exchange on SBS 2003

I currently have Vista and Outlook 2007.
My email, contacts and calendar are all in a OST file, which syncs to our Windows SBS 2003 server and the Exchange installed on it.
How should I configure my iPhone and iTunes, in order to have my calendar in iPhone?
After trying for several times to sync through iTunes without any success (could never have any items imported to the iPhone) I did create an Exchange account on my iPhone with the IP address of our SBS server, and my account details, and now all my items seem to appear (however they all have Accept/Maybe/Refuse buttons).
Is this the correct way? Will I get alarms for my appointments, even if I don't accept them on the iPhone?
Thank you!

OK, I think I figured it out, with Apple's iCloud instructions and a little help from campus tech support. This only applies to people using Outlook with Microsoft Exchange.
Enable iCloud on your computer (running Lion) and your iPhone. http://www.apple.com/icloud/setup/mac.html
Then go to your iPhone's Mail icon, click on Add Account > Microsoft Exchange and enter your login info.
Doing this transferred my work email and calendar to my phone wirelessly.

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 R2 premium (with ISA 2004) Exchange ActiveSync not working

A client has a SBS 2003 R2 premium (with ISA 2004) and wants to sync iPhones and Android phones.
When using the Microsoft Remote Connectivity Analyzer and selecting 'Exchange ActiveSync' we get 'The test of the FolderSync command failed. Exchange ActiveSync returned an HTTP
500 response.'
We tried every solution we could find on the internet, without success.
This is what we tried and checked so far:
- fixed IP, DNS, trusted SSL (comodo) seem all OK
- Exchange 2003 SP2 and ISA 2004 SP3 installed.
- RWW and OWA working fine.
- tests with iPhone and Android -> 'cannot get mail. The connection to the server failed'.
- event viewer reveals no further clues.
- ran CEICW several times enabling and disabling most remote options (OWA OMA,...)
- manually checked all vDir settings in IIS6
- tested with different accounts, created a testaccount without any administrative privileges in Active Directory.
- surfing to servername/microsoft-server-activesync from local network and to domain/microsoft-server-ActiveSync from external computer both give: HTTP 501/HTTP 505 error as expected.
- reset the default virtual directories
- on ISA a query by dest port (443) shows traffic reaching the ISA server ending in:
Log type:
Web Proxy (Reverse)
Status:
500 Internal Server Error
Rule:
SBS OMA Web Publishing Rule
Source:
External ( XX.XX.XX.XX:0)
Destination:
( XX.XX.XX.XX:443)
Request:
POST
Filter information:
Req ID: 1c6d0bea
Protocol:
https
User:
anonymous
Could anyone give me any pointers on what I need to do to get this working please?
Many thanks in advance for your assistance.
Regards
Jean-Paul Laffargue
ARCOM BVBA

I used to have a SBS2003 on ISA running activesync with no issues so I'll try and give you guidance although it's been a while. I gather this is the first time use of this feature on this SBS? If so make sure you follow the instructions here:
http://technet.microsoft.com/en-us/library/cc182239.aspx
Also make sure you've enabled all mobile services in exchange features and updated your users with the Mobile User profile (I think they need to be members of the Mobile and Remote Web Workplace groups in Manage Users IIRC). Anything in the event logs?
Also, for some phones you need to manually download the certificate if you use a self-signed type.
Note that in the end it may be time to replace this soon to be unsupported ISA with a separate firewall (or a "free" Untangle box) and go to a one NIC solution. It simplifies things and you need to do that anyway to transition off SBS2003 when it is
unsupported next year.
-- Al

Getting iPhone 3G (2.1) to sync with Exchange SBS 2003

Hi all.
I am a rather n on-technical person wishing to get some help troubleshooting my problem.
I have the above new iPhone needing to sync with my calendar, ctcs and email on my work Exchange SBS 2003.
Really need someone kind (and patient?!) enough to take me from the start. Setting up the phone has been easy enough, I think it is the server end that is my real problem.
Have had a Windows Mobile device working exactly as I want the iPhone to work over the last 15 months.
Heeeeelp please....

As I read you updated your iPhone to 2.2.1. That means that maybe this cause the problem.
Sometimes when I connect my iPhone to iTunes I saw the message what says that "iTunes was unable to connect to the iPhone... " but if I reconnect my iPhone then iTunes recognize my phone and everything is OK.
If the reconnecting does not help you then I advise that reset your iPhone with 'Erase All Data and Settings'. Settings > General > Reset > Erase All Data and Settings.
If you reset your iPhone with 'Erase All Data and Settings' then your iPhone will delete your files and also the 2.2.1 software update and after that it will run with the original software what you bought with it.
The reset takes approximately 2 hours. And this is delete everything from your iPhone.
So, as it seems you can't back up your iPhone, that means everything what is on your iPhone will be deleted except if you don't have them on your computer.
After you reseted your iPhone, try to connect with iTunes. If it won't works then try it on an another Mac or PC and if you can't sync your iPhone at all, you have to take your iPhone to your carrier for a service.
Important note: After you reseted your iPhone, it will please that connect to iTunes to activate the phone. If you can't connect to iTunes your phone, you won't be able to use it!
As you know, without activating you can't use the iPhone.
If you can do the activation then you probably will be able to sync it.
If you can't be without mobile phone and just the iPhone what you've then don't do that until you maybe could miss your phone (I mean if you iPhone have to be serviced).

Any possibility to restore Public Folders when priv1.edb priv1.stm and pub1.edb pub1.stm files was moved?

Hello, good people
(I am sorry for my english)
introduction:
MS Server 2003, Exchange 2003, Eset Endpoint Protection.
We ned some free space on hdd.
taken steps:
1. Dismounted public and private stores
2. priv1.edb priv1.stm pub1.edb pub1.stm files moved to Z:\post (Z: - network drive on NAS)
3. was created new private an public sores.
4. mounted
results:
1. Some strange behavior in email flow - messages stucks in local delivey queue, does not reaches recipients,ect.
2. Lost folder "tree" in Public folders - i mean, now there is only one folder - Internet Newsgroup
Question:
Is there any possbility to "restore" public folder ?
thanks a lot.

Hi I agree with Belinda if the issue is used size on the server perform an offline defrag on all the original DB.
Have a look here for how to:
https://social.technet.microsoft.com/Forums/en-US/7bc0be32-584a-4940-a3ad-b56aa01a6b1f/exchange-2003-reclaim-white-space?forum=exchangesvrgenerallegacy
You should maybe talk to your storage guy to see if your NAS is compliant with exchange:
http://support.microsoft.com/kb/317173
http://support.microsoft.com/kb/839687
(careful:
Supportability
If you use Exchange 2003 incorrectly with a network-attached storage product, you may experience data loss, including a total loss of the Exchange database files.

Error connecting win 8.1 to sbs 2003 vpn

When I attempt to connect my (all antivirus off, firewall off, ports forwarded, gre enabled) win 8.1 laptop to my office sbs 2003 machine through a pptp vpn, I get an error. Here is the log:
[cmdial32] 21:34:36
11 Custom Action Failed
ActionType = Connect Actions Description = Configure proxy settings for IE. ActionPath = C:\Users\******\AppData\Roaming\Microsoft\Network\Connections\Cm\REMOTE\CMPROXY.DLL. This action either could not be loaded, or failed to run.
[cmdial32] 21:34:36
21 On-Error Event
ErrorCode = 1157 ErrorSource = Configure proxy settings for IE.
Any ideas? Thanks in advance.

Hi,
Regarding the current issue, please try to refer to the following similar thread to see if it works.
Windows SBS PPTP VPN Issues
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_23198820.html
In addition, I suggest you could refer to the following method to join it to the domain over VPN.
Joining a computer to a domain over a client VPN connection
https://msmvps.com/blogs/acefekay/archive/2012/01/18/joining-a-computer-to-a-domain-over-a-client-vpn-connection.aspx
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

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

SBS 2011; Exchange ActiveSync problems in the middle of a migration

Hi
We're in the middle of a migration from SBS 2003 to SBS 2011 and are stuck in the lengthy process of moving users' mailboxes.
At this point, I have about 20 percent of the users' email on the SBS 2011 box, and the rest still on the SBS 2003 box.
Right now I have to quickly deal with an issue that's cropped up with Exchange ActiveSync:
I ran the Connectivity Analyzer for a user (this one's box had been migrated) and got the error below. By the looks of the error, I don't think it matters where the mailbox happens to reside ...
The SBS 2011 box has been set up using a migration install and the procedures listed in the MS migration docs.
At the rate we're going, it's still going to take a while to migrate these mailboxes. (The fact that they began tonight was actually an accident.) If mobile users can't get their mail, I'm going to have a big mess on my hands ...
What do I need to do to get this running properly for all users?
Thanks
CL
An ActiveSync session is being attempted with the server.
Errors were encountered while testing the Exchange ActiveSync session.
Additional Details
Elapsed Time: 793 ms.
Test Steps
Attempting to send the OPTIONS command to the server.
The OPTIONS response was successfully received and is valid.
Additional Details
HTTP Response Headers:
MicrosoftOfficeWebServer: 5.0_Pub
Pragma: no-cache
Public: OPTIONS, POST
Allow: OPTIONS
MS-Server-ActiveSync: 6.5.7638.1
MS-ASProtocolVersions: 1.0,2.0,2.1,2.5
Content-Length: 0
Date: Fri, 30 May 2014 08:49:48 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Elapsed Time: 205 ms.
Attempting the FolderSync command on the Exchange ActiveSync session.
The test of the FolderSync command failed.
Additional Details
An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: <body><h2>HTTP/1.1 403 Forbidden</h2></body>
HTTP Response Headers:
MicrosoftOfficeWebServer: 5.0_Pub
Pragma: no-cache
MS-Server-ActiveSync: 6.5.7638.1
Content-Length: 44
Content-Type: text/html
Date: Fri, 30 May 2014 08:49:48 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Elapsed Time: 588 ms.

Hi --
Neither of the Exchange servers is publicly listed as the mail handler for this domain. Mail is preprocessed by a cloud spam filtering service before coming down. So I expect no changes in MX records -- not even a change in the spam filter's delivery IP
address, since that points to my firewall. I'll forward SMTP traffic to the new server when the time comes.
I was told by MS that moving the mailboxes would not disrupt anything as long as both SBS boxes were up and running. And despite what the Connectivity Analyzer showed, people in this office have been receiving email on their mobile phones all day. I've had
a few sporadic reports of people supposedly not getting email on their smartphones, but I can't see how anything I did (basically just move mailboxes at this point) could allow some people's phones to get mail while others' can't, when everyone was getting
mail yesterday.
I also have an odd report from someone who claims that his mobile phone is processing email just fine, but his MacBook running Entourage suddenly can't connect.
Oh well ... The day is over (at least for the workers). Hopefully by the time the workers return on Monday, I'll be back to having just one SBS box on the network.
The mailboxes are being moved A LOT faster than any of the documents I read warned me they would. One document said that a 75 GB database could take close to 48 hours to transfer. And this server's Exchange database was 67 GB ... But last night's
"accident" (I thought I was only prepping a new database when in fact the machine was actively moving email into it) resulted in about 40% of the mailboxes being completely moved by 8 a.m.. And since 5 p.m., when I restarted the move requests,
the machine has completed the moves of about 20% more mailboxes. So I expect this part to be over probably by early morning. (The ones that remain are the really big ones -- still, after I spent a week doing mailbox housekeeping.)
I was also warned about the lengthy conversion requirements for the public folders. I transferred those last weekend. The whole process was over with in less than four hours. Go figure ...
(The public folder transfer did have an annoying side effect -- I kept receiving warning after warning via email from the SBS 2003 box about a high number of items in Exchange's send queues ...)
Thanks
CL

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

Does SBS 2003 need M$SQL Server?

Hi All,
I have just picked up a new customer with SBS2003. (I can not tell if it is R1 or R2.) He is using it primarily as an Exchange Server and to share files with Quick Books. The server has M$SQL 2005 installed on it. The server is "refurbished".
His backup is horrible and he does use RAID.
The original consultant has moved to another state. For backup proposes, I inquired of him as to why he had M$SQL installed. This came back from him:
"Exchange does not use SQL. however, SQL is a core service in Windows Small Business Server (SBS). It holds databases for sharepoint and performance metrics for components of SBS. It's a major piece and SBS would be unstable without
it. "
Huh?
"Sharepoint" is a web development tool. Is it even part of SBS 2003?
What "Performance metrics"?
Since when is SBS2003 "unstable" without any SQL server installed?
Am I missing something? 2005 sql server only came with the more expensive version of R2. If this is R1, M$SQL 2005 was not invented yet!
Anyway, I'd appreciate an education here.
Many thanks, -T

You can still order SBS 2011 from legit sources on the web and rumor has it from HP. But you don't have to purchase the hardware at the same time as the software. I don't think the sky will fall in April, but it is definitely time to move on in a planned
way. I see SBS 2011 for less than 1K USD on the net. Compare that to replacing with standard Exchange and Server at a cost of 4K and up.
SBS 2011 will be supported until 2020 giving you and your customer time to plan for the next round.
Alternatives are Server 2012 Essentials (Role or SKU) and hosted email.
Hi Larry,
His current system works. He sees no economic justification to upgrade to a slower, buggier, more complicated server. He also can not afford it. If his current "refurbished" server dies, it would be better to put him on Zoho mail
at about $30.00 per month. If he still wants his own hardware, Zimbra or Open Change on Scientific Linux / Cent OS would be only the cost of the hardware and the set up fee. It would give him a lot more stability and software that can be easily
upgraded. If he really wants to stay with Windows Server, I do like your sbs2011 idea. Better all around if he goes with Zoho or gMail. (I am surprised he hasn't been eaten alive with spam.) Thank you!
-T

SBS 2003 Exchange pub1.edb daily growth

Similar Messages

Maybe you are looking for