Solved

SBS 2008 not PDC & Autodiscover problem

Posted on 2012-03-20
3
522 Views
Last Modified: 2012-06-14
Hello, I am having 2 problems with a server

1) I used to have an old SBS 2008 Premium which hardware failed and so we had to install a new SBS 2008 Premium on new hardware.

For some reason (Maybe something related to the FSMO roles), after running a BPA (Best Practices Analyzer) I got as a result this errors:

BPA Error
How should I make this the only server on the network and delete all traces of old server?

2) On Exchange and I dont know if it might be related to the previous problem, I run TestExchangeConnectivity and I get an autodiscover error that I cant get to solve.

This is the error:

AutoDiscover
Thanks everyone for tips and tricks to solve this problems.
0
Comment
Question by:SyncroIT
  • 2
3 Comments
 
LVL 38

Accepted Solution

by:
Adam Brown earned 500 total points
ID: 37743697
1. Seize the FSMO roles that belonged to the old server and run a meta data cleanup on AD for the old server.
Seize Roles: http://support.microsoft.com/kb/255504
Clean up Metadata: http://technet.microsoft.com/en-us/library/cc736378%28v=ws.10%29.aspx

2. You need to have a public CNAME or A record in your DNS records that points autodiscover.domain.com to your public IP address. Have you configured that yet?

There's more information on setting up Autodiscover here as well: http://www.thirdtier.net/2009/02/setting-up-an-external-autodiscover-record-for-sbs-2008/
0
 

Author Comment

by:SyncroIT
ID: 37747599
Hello, thank you for your answer, will running the Seize commands require a server restart right?

How do I delete de "oldServer" from the Server Configuration list in Exchange Management Console?

I am having a lot of problems now with users which computers are on the domain getting password prompts on their Outlooks.

I am changing the DNS to be able to configure an autodiscover SRV record, but this will take a couple of days for national NIC to replicate.

Thanks!
0
 
LVL 38

Expert Comment

by:Adam Brown
ID: 37748364
The seize shouldn't require a reboot. To delete the old server from Exchange, open ADSIEdit and connect to the Configuration section. Navigate to Services\Microsoft Exchange\First Organization\Administrative Groups\Exchange Administrative Group (FYDIBOHF23SPDLT)\Servers and delete the old server from there.

For the password prompt thing, are any of the users opening sharepoint folders or other mailboxes? Make sure the only thing listed in their Outlook profile is their own mailbox and see if the prompts continue.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now