Prev: Blocked by cbl.abuseat.org
Next: sbs2008 standard Outlook 2007 client always asks for credentials
From: Cliff Galiher - MVP on 28 May 2010 20:37 Start at the top and for each warning and error, read the KB article. Should get you straightened out. -- Cliff Galiher Microsoft has opened the Small Business Server forum on Technet! Check it out! http://social.technet.microsoft.com/Forums/en-us/smallbusinessserver/threads Addicted to newsgroups? Read about the NNTP Bridge for MS Forums. "pcraig11" <pcraig11.4bow9d(a)DoNotSpam.com> wrote in message news:pcraig11.4bow9d(a)DoNotSpam.com... > > Ok, so this is what the IT health scan looks like on the new Server 2008 > server: > > Errors and warnings Show all checks > > > Data collection errors Errors: 1 > SysVol > Error: Analysis report failure: check id 36 does not link to > error/warning/info id 3703 > > > Network Connectivity Completed > Server names resolve correctly > Completed > > Active Directory is connected to all domain controllers > Completed > > Remote WMI access is enabled on servers > Completed > > Servers can be queried using DNS > Completed > > Time service is running on all domain controllers > Completed > > Exchange service is installed > Completed > > DSAccess is configured correctly > Completed > > Netlogon service is running on all domain controllers > Completed > > > > Active Directory Site Configuration Errors: 2 > Inter-site topology generation is enabled for the Knowledge Consistency > Checker > Completed > > Intra-site topology generation is enabled for the Knowledge Consistency > Checker > Completed > > Local Active Directory site contains only local subnets > Completed > > Universal group membership is cached > Completed > > Domain controllers are holding roles > Error: The THEGIANTNUT.tristatefast.local domain controller is not > holding the PDC role. > See also: KB 223346 > Error: The thelittlenut.tristatefast.local domain controller is not > holding the PDC role. > See also: KB 223346 > > Active Directory site is contained in a site link > Completed > > Connection translation is enabled and a global catalog exists > Completed > > Interval for tombstone lifetime is set correctly > Completed > > Inbound replication is enabled > Completed > > Outbound replication is enabled (for writable domain controllers only) > Completed > > Infrastructure master is not a global catalog server > Completed > > > > Active Directory Subnet Configuration Completed > Subnets are associated to Active Directory sites > Completed > > Subnets are defined in Active Directory > Completed > > Subnet definitions are consistent in Active Directory > Completed > > Active Directory site contains a subnet definition > Completed > > > > Active Directory Replication Completed > Domain controller replicates within the timeout threshold > Completed > > Allow Replication With Divergent and Corrupt Partner is disabled > Completed > > Domain, Schema, and Configuration naming contexts are defined > Completed > > Naming context replicated successfully > Completed > > > > File Replication and SYSVOL Administration Warnings: 1, Skipped: 5 > The File Replication Service and the DFS Replication services are > running > Completed > > Domain controller replicates within the timeout threshold > Warning: The THEGIANTNUT.tristatefast.local domain controller in the > local Active Directory site did not replicate within 15 minutes. > See also: KB 249256 > > Sufficient free space exists on the SYSVOL partition > Skipped: Check was skipped due to data collection errors > > Sufficient free space exists for the SYSVOL staging folder > Skipped: Check was skipped due to data collection errors > > Domain controllers do not have morphed folders > Skipped: Check was skipped due to data collection errors > > SYSVOL staging area has sufficient free space > Skipped: Check was skipped due to data collection errors > > SYSVOL local path can be read from the registry. > Skipped: Check was skipped due to data collection errors > > > > DNS Verification Completed > Start of Authority resource record was found > Completed > > Glue records can be resolved > Completed > > GUID CNAME records can be resolved > Completed > > DNS delegation is functioning > Completed > > Domain controllers are not hosting the root DNS zone > Completed > > Domain controllers are using static IP addresses > Completed > > Domain controllers are associated to a domain zone > Completed > > DNS records can be resolved > Completed > > Forwarders are configured and root hints are enabled > Completed > > Scavenging interval is set correctly for a zone > Completed > > > > Network Adapter Configuration Completed > Domain controllers are not listening on multiple addresses > Completed > > DNS servers are not listening on multiple addresses > Completed > > Orphaned network interface objects do not exist > Completed > > Domain controllers reference a valid DNS server > Completed > > Binding order is set correctly > Completed > > APIPA addresses are not used > Completed > > Dynamic registration is configured correctly > Completed > > Gateway address is in the same network as the IP address and subnet mask > > Completed > > Computer is not connected to the same network multiple times via > different network adapters > Completed > > > > Domain Controller Health Completed > Volume that contains the operating system has greater than 1 GB of free > space > Completed > > Volume that contains the operating system has greater than 100 MB of > free space > Completed > > > > Network Time Protocol Configuration Warnings: 2 > Clock offset for domain controllers is within five minutes of the PDCE > Completed > > Domain controllers that are configured to use Network Time Protocol > (NTP) have NTP servers defined > Completed > > PDCE of the root domain is configured to synchronize with a reliable > time source > Completed > > Domain controllers are configured to allow time corrections that are > less than two days > Warning: The THEBIGNUT.tristatefast.local domain controller is > configured to allow time corrections that are greater than 172800 > seconds. > See also: KB 884776 > Warning: The thelittlenut.tristatefast.local domain controller is > configured to allow time corrections that are greater than 172800 > seconds. > See also: KB 884776 > > Time sources are defined correctly for domain controllers > Completed > > > > Exchange Server Configuration Errors: 1 > Exchange Server is using domain controllers within the same local Active > Directory site > Completed > > LDAP filters are valid > Completed > > Public Folders container exists under All Address Lists in Active > Directory > Completed > > Public Folders container allows inheritable permissions > Completed > > All Address Lists container allows inheritable permissions > Completed > > Recipient Policy names do not contain leading and trailing spaces > Completed > > Exchange organization is running in native mode > Error: The Exchange organization is running in mixed mode. Consider > changing the mode to native. > See also: KB 327779 > > Recipient policies use supported SMTP address format > Completed > > Exchange organization does not contain a server running Exchange Server > 5.5 > Completed > > Exchange organization does not contain Active Directory Connectors > Completed > > Exchange Server 2003 service packs are installed > Completed > > Exchange Server 2000 service packs are installed > Completed > > Exchange 2000 Server software updates are installed > Completed > > > > Network Configuration Completed > IP addresses are valid in the network > Completed > > Network adapters are configured with the correct gateway > Completed > > > > Event Log Entries Warnings: 1 > System Log, Netlogon, Event ID 5774 > Completed > > System Log, Netlogon, Event ID 5775 > Completed > > System Log, Netlogon, Event ID 5781 > Completed > > System Log, EventLog, Event ID 6008 > Completed > > System Log, W32Time,Event ID 36 > Completed > > System Log, W32Time, Event ID 29 > Warning: Event 29 was reported on the thelittlenut.tristatefast.local > computer. Time: 5/27/2010 8:54:11 PM. Type: Error. Source: W32Time. > Category: 0. User: . Computer: THELITTLENUT. Description: The time > provider NtpClient is configured to acquire time from one or more time > sources, however none of the sources are currently accessible. No > attempt to contact a source will be made for 15 minutes. NtpClient has > no source of accurate time. . > See also: KB 957009 > > System Log, SAM, Event ID 16645 > Completed > > System Log, NTFS, Event ID 55 > Completed > > Directory Service Log, Global Catalog, Event ID 1110 > Completed > > Directory Service Log, NTDS General, Event ID 2103 > Completed > > File Replication Service Log, NtFrs, Event ID 13510 > Completed > > File Replication Service Log, NtFrs, Event ID 13511 > Completed > > System Log, Ftdisk, Event ID 57 > Completed > > File Replication Service Log, NtFrs, Event ID 13568 > Completed > > Directory Service Log, NTDS ISAM, Event ID 467 > Completed > > File Replication Service Log, NtFrs, Event ID 13561 > Completed > > System Log, Kerberos, Event ID 4 > Completed > > P.S.-Sorry for all of the long reports and log files, but I just dont > want to miss anything! > > Thanks again > > > -- > pcraig11 > ------------------------------------------------------------------------ > pcraig11's Profile: http://forums.techarena.in/members/224993.htm > View this thread: > http://forums.techarena.in/small-business-server/1340886.htm > > http://forums.techarena.in >
From: pcraig11 on 29 May 2010 12:13 Will do....but from what I have read, the other DC's, not the SBS server, cant hold the PDC role....so why would that show as an error and not as a warning? thanks -- pcraig11 ------------------------------------------------------------------------ pcraig11's Profile: http://forums.techarena.in/members/224993.htm View this thread: http://forums.techarena.in/small-business-server/1340886.htm http://forums.techarena.in
From: Cliff Galiher - MVP on 29 May 2010 18:41 Because the IT Health Scanner is not an SBS specific tool. It scans your systems and looks for *problems* in Active Directory. Some problems are "warmings" in that they indicate an issue, but won't impact the day-to-day operation of the server, while others are "errors" because the server itself have severe issues caused by the problem reported. -- Cliff Galiher Microsoft has opened the Small Business Server forum on Technet! Check it out! http://social.technet.microsoft.com/Forums/en-us/smallbusinessserver/threads Addicted to newsgroups? Read about the NNTP Bridge for MS Forums. "pcraig11" <pcraig11.4bqftb(a)DoNotSpam.com> wrote in message news:pcraig11.4bqftb(a)DoNotSpam.com... > > Will do....but from what I have read, the other DC's, not the SBS > server, cant hold the PDC role....so why would that show as an error and > not as a warning? > > thanks > > > -- > pcraig11 > ------------------------------------------------------------------------ > pcraig11's Profile: http://forums.techarena.in/members/224993.htm > View this thread: > http://forums.techarena.in/small-business-server/1340886.htm > > http://forums.techarena.in >
From: pcraig11 on 31 May 2010 20:45 ***SOLVED***** Thanks for all of your help. Since time was of the essence, because the system was down, I decided to copy the SYSVOL share from the SBS server to the new server manually. After I completed that process, I transferred the FSMO roles to the new server, and ran DCPROMO to demote the old SBS server. Everything seemed to work out fine. Thanks for all of your help, time and consideration. -- pcraig11 ------------------------------------------------------------------------ pcraig11's Profile: http://forums.techarena.in/members/224993.htm View this thread: http://forums.techarena.in/small-business-server/1340886.htm http://forums.techarena.in
First
|
Prev
|
Pages: 1 2 3 Prev: Blocked by cbl.abuseat.org Next: sbs2008 standard Outlook 2007 client always asks for credentials |