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.

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

  • 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

  • How do I get our iPhones Calendar, to sync to a 2003 exchange server?

    What on the 2003 exchange server need to be turned on?
    I went to a sister plant and they added me to there exchange server, and now I can add to my calander on the phone fine, and it show up on the
    PC outlook 2010 calender fine.

    http://support.google.com/mobile/bin/answer.py?hl=en&topic=14252&answer=138740

  • 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

  • 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 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.Zabransky

    Hi 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

  • 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

  • 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 ---&gt; 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&amp; entry, String&amp; 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!

  • MacBook 10.4.7 not talking to Windows 2003/Exchange server

    Hi folks
    Have a new MacBook 2GHz running 10.4.7, trying to talk to a Windows 2003 network at work. Services needed are Exchange server support (for Microsoft Entourage) and some shared drives over a domain on the Windows server machine. Experiencing problems with both!
    Re. shared drives, browsing the network via Finder window sporadically shows up some or all of the Windows machines connected to the network, and the shared drive. It is possible to connect to some of the Windows machines directly, although this is inconsistent. However when attempting to connect to the shared drive, the alias appears correctly, but filling in the details (workgroup, name and password) just leads to an error message saying that the alias could not be found, with the option to delete or fix the alias. Fixing opens up another Finder window but the network is greyed out so you can't point to the shared drive!
    Attempting to connect via Connect To Server, either by browsing or entering the smb address line, also allows one to enter the workgroup, name and password, but simply says 'could not connect to the server because the name or password is not correct' (even though it is).
    Firewall is on but allowing Windows Sharing. AppleTalk is active. Connecting over a wireless network but ethernet connection seems to make no odds.
    In terms of Entourage, the system simply wont find the Exchange server, which I'm presuming may be symptomatic of whatever is causing the above!
    Any help/ideas/thoughts most gratefully received.
    Cheers
    Dan
    MacBook 2GHz   Mac OS X (10.4.7)  

    I hope this helps.  But, Apple has confirmed a significant bug in 10.7.4 that breaks SMB.  Their support says they are working on it, but they do not know when the fix will be released.  It has broken SMB at all sites I support including my own location where Lion server has the updated version as well.  Only AFP works but not consistently.  The suggestion is to restore 10.7.3 from a backup or wait until the fix is released.  SMB does work - but only when admin authentication is used on Mac servers - don't know about Windows Servers.  I do know the client side of Mac's also are affected with SMB issues.  Good luck!

  • Microsoft 2003 exchange server

    I'm trying to set up my work e-mail to my ipad2. The work server is running on Microsoft exchange 2003, I have all the settings that I need wich are being used by fellow workers on their I phones but my iPad2 keeps telling me it can't verify the account. Is there some thing else I need to do on the iPad or on the exchange server and what? Any help much appreciated.

    Hi,
    Thank you for posting in Windows Server Forum.
    Which version of MRD version you are using for remote session?
    From MAC device suggest you to try new MRD 8.0.10 and verify whether you are facing same issue.
    Can you achieve you functionality from Microsoft client system?
    Can you collect logs whether there is useful information related to this issue?
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • 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+

  • 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

  • Exchange Server 2003 :: ActiveSync :: Unable to send out attachments

    Hi All,
    I am facing a weird issue with SBS 2003 (windows server 2003 sp2 with microsoft exchange 2003 sp2) Microsoft Exchange ActiveSync. ActiveSync users are able to configure the devices just fine, send and receive email fine as well but when they try to send
    any attachment the email will stay in the outbox.
    So far i have tried the following fixes
    made sure the permissions on the exchange vdirs and activesync vdir are correct
    c:\windows\temp and %temp% location has read/write access to authenticated users
    uploadreadaheadsize (thru adsutil.vbs) and messagesizelimit for oma reg key are bumped up (20MB each)
    testremoteexchange connectivity analyzer shows all green
    Now, if i make user the member of administrators group and try to send an email with attachment (i am sending a screenshot of 2.3mb) it goes out fine.
    IIS logs shows HttpServerStatusError 500used logparserstudio to parse the iis file
    cs-username
    cs-uri-stem
    HTTPstatus
    w3-status-details
    domain\testas
    /Microsoft-Server-ActiveSync
    500
    HttpStatusServerError
    any pointers how this issue can be dealt with and resolved, will be appreciated.
    Regards,
    Nav
    Regards, Navdeep [a.k.a v-2nas]

    any ninjas out there to crack this problem........
    Regards, Navdeep [a.k.a v-2nas]

  • Problems using Outlook 2013 with Exchange Server Small Business Server 2003

    Hello,
    We have just upgraded our Office suite from Office 2007 Pro to Office 2013 Pro.  When I try to configure Outlook 2013 to connect to Exchange Server 6.5 (SMS 2003) I get an error "Outlook 2013 being blocked by current version of Exchange Server".
     Outlook 2013 at present is not communicating with Exchange server 6.5
    Are there any fixes I have to install on our SMS 2003 server to allow Outlook 2013 to work with SMS 2003 Exchange Server?
    Any configuration changes I need to make?  Any help is appreciated.
    Thx
    John G.
    John Grace

    Hi
    Outlook 2013 is not supported with exchange 2003:
    http://technet.microsoft.com/en-us/library/ee624351.aspx#section10
    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.

Maybe you are looking for