Location not populating new sites
-
Wednesday, May 23, 2012 7:15 PMI have added 2 new sites to my domain. the sites show up in sites and services, but "location" does not. when adding a printer through print management of searches through AD, the " location" shows the existing "older" sites only as choices.
The Big Lug
All Replies
-
Wednesday, May 23, 2012 9:58 PM
I think that this is due to AD replication latency or replication issues.
Please run dcdiag /v /e against DCs you have and check if there is errors.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Microsoft Student Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer -
Thursday, May 24, 2012 3:19 AM
Have you verified the health of DC run dcdiag and repadmin /replsum output and post the same also check the event log for any warning or errors.It seems that there is replication issue or if you have justed added the site you need to wait for the replication to complete.
Best Regards,
Sandesh Dubey.
MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. -
Thursday, May 24, 2012 4:50 AM
Beginning data collection for replication summary, this may take awhile:
.................
Source DSA largest delta fails/total %% error
C-HOLDCOSRV02 54m:29s 0 / 63 0
CHRSERV03 54m:29s 0 / 48 0
DESTMX01 53m:20s 0 / 12 0
DESTVPN >60 days 2 / 48 4 (1256) The remote system is
not available. For information about network troubleshooting, see Windows Help.
HH-SERV03 23m:05s 0 / 43 0
HH-SERV04 23m:38s 0 / 20 0
HH-SERV05 15m:24s 0 / 55 0
HONSERV02 15m:24s 0 / 25 0
HONSERVER01 50m:34s 0 / 50 0
HYUSERV02 55m:53s 0 / 35 0
MAZSERV01 15m:26s 0 / 45 0
MAZSERV02 15m:26s 0 / 40 0
TOYSERV06 15m:25s 0 / 45 0
TOYSERV07 51m:53s 0 / 30 0
Destination DSA largest delta fails/total %% error
C-HOLDCOSRV02 48m:21s 0 / 43 0
CHRSERV03 54m:10s 0 / 48 0
DESTMX01 54m:37s 0 / 12 0
DESTVPN 55m:26s 0 / 43 0
HH-SERV03 23m:23s 0 / 30 0
HH-SERV04 22m:54s 0 / 35 0
HH-SERV05 08m:10s 0 / 40 0
HONSERV02 48m:35s 0 / 43 0
HONSERVER01 >60 days 2 / 45 4 (1256) The remote system is
not available. For information about network troubleshooting, see Windows Help.
HYUSERV02 15m:00s 0 / 50 0
MAZSERV01 10m:00s 0 / 40 0
MAZSERV02 01m:47s 0 / 50 0
TOYSERV06 51m:33s 0 / 40 0
TOYSERV07 12m:20s 0 / 40 0The Big Lug
-
Thursday, May 24, 2012 4:51 AM
......................... ForestDnsZones passed test
CrossRefValidationRunning partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidationRunning partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidationRunning partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidationRunning partition tests on : azizco
Starting test: CheckSDRefDom
......................... azizco passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... azizco passed test CrossRefValidationRunning enterprise tests on : azizco.com
Test omitted by user request: DNS
Test omitted by user request: DNS
Starting test: LocatorCheck
GC Name: \\C-HoldCoSRV02.azizco.com
Locator Flags: 0xe00011bd
PDC Name: \\C-HoldCoSRV02.azizco.com
Locator Flags: 0xe00011bd
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
1355
A Good Time Server could not be located.
KDC Name: \\C-HoldCoSRV02.azizco.com
Locator Flags: 0xe00011bd
......................... azizco.com failed test LocatorCheck
Starting test: Intersite
Doing intersite inbound replication test on site Honda:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site Honda is: HONSERVER01.
Checking for down bridgeheads ...
Bridghead Chrysler\CHRSERV03 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
*Warning: Remote bridgehead Hyundai\DESTVPN is not eligible as a
bridgehead due to too many failures. Replication may be
disrupted into the local site Honda.
Bridghead Chrysler\C-HOLDCOSRV02 is up and replicating fine.
Bridghead Toyota\TOYSERV06 is up and replicating fine.
Bridghead Mazda\MAZSERV01 is up and replicating fine.
Bridghead Mazda\MAZSERV02 is up and replicating fine.
Bridghead Hyundai\HYUSERV02 is up and replicating fine.
Bridghead Honda\HONSERV02 is up and replicating fine.
Bridghead Chrysler\DESTMX01 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Bridghead Toyota\TOYSERV07 is up and replicating fine.
Doing in depth site analysis ...
Remote site Hyundai is replicating to the local site Honda the
writeable NC ForestDnsZones correctly.
Remote site Hyundai is replicating to the local site Honda the
writeable NC DomainDnsZones correctly.
Remote site Hyundai is replicating to the local site Honda the
writeable NC Schema correctly.
Remote site Hyundai is replicating to the local site Honda the
writeable NC Configuration correctly.
Remote site Hyundai is replicating to the local site Honda the
writeable NC azizco correctly.
Remote site Toyota is replicating to the local site Honda the
writeable NC ForestDnsZones correctly.
Remote site Toyota is replicating to the local site Honda the
writeable NC DomainDnsZones correctly.
Remote site Toyota is replicating to the local site Honda the
writeable NC Schema correctly.
Remote site Toyota is replicating to the local site Honda the
writeable NC Configuration correctly.
Remote site Toyota is replicating to the local site Honda the
writeable NC azizco correctly.
Remote site Chrysler is replicating to the local site Honda the
writeable NC ForestDnsZones correctly.
Remote site Chrysler is replicating to the local site Honda the
writeable NC DomainDnsZones correctly.
Remote site Chrysler is replicating to the local site Honda the
writeable NC Schema correctly.
Remote site Chrysler is replicating to the local site Honda the
writeable NC Configuration correctly.
Remote site Chrysler is replicating to the local site Honda the
writeable NC azizco correctly.
Remote site Mazda is replicating to the local site Honda the
writeable NC ForestDnsZones correctly.
Remote site Mazda is replicating to the local site Honda the
writeable NC DomainDnsZones correctly.
Remote site Mazda is replicating to the local site Honda the
writeable NC Schema correctly.
Remote site Mazda is replicating to the local site Honda the
writeable NC Configuration correctly.
Remote site Mazda is replicating to the local site Honda the
writeable NC azizco correctly.
Remote site Hastings is replicating to the local site Honda the
writeable NC ForestDnsZones correctly.
Remote site Hastings is replicating to the local site Honda the
writeable NC DomainDnsZones correctly.
Remote site Hastings is replicating to the local site Honda the
writeable NC Schema correctly.
Remote site Hastings is replicating to the local site Honda the
writeable NC Configuration correctly.
Remote site Hastings is replicating to the local site Honda the
writeable NC azizco correctly.
Remote site 4716 is replicating to the local site Honda the
writeable NC ForestDnsZones correctly.
Remote site 4716 is replicating to the local site Honda the
writeable NC DomainDnsZones correctly.
Remote site 4716 is replicating to the local site Honda the
writeable NC Schema correctly.
Remote site 4716 is replicating to the local site Honda the
writeable NC Configuration correctly.
Remote site 4716 is replicating to the local site Honda the
writeable NC azizco correctly.
Doing intersite inbound replication test on site Hyundai:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site Hyundai is: DESTVPN.
Checking for down bridgeheads ...
Bridghead Chrysler\CHRSERV03 is up and replicating fine.
Bridghead Hyundai\DESTVPN is up and replicating fine.
Bridghead Chrysler\C-HOLDCOSRV02 is up and replicating fine.
Bridghead Honda\HONSERV02 is up and replicating fine.
Bridghead Chrysler\DESTMX01 is up and replicating fine.
Bridghead Mazda\MAZSERV01 is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead Toyota\TOYSERV06 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Bridghead Hyundai\HYUSERV02 is up and replicating fine.
Bridghead Mazda\MAZSERV02 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Hyundai.
Doing intersite inbound replication test on site Toyota:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site Toyota is: TOYSERV07.
Checking for down bridgeheads ...
Bridghead Chrysler\CHRSERV03 is up and replicating fine.
Bridghead Toyota\TOYSERV07 is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
Bridghead Chrysler\C-HOLDCOSRV02 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead Hyundai\HYUSERV02 is up and replicating fine.
Bridghead Mazda\MAZSERV01 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Bridghead Toyota\TOYSERV06 is up and replicating fine.
Bridghead Hastings\HH-SERV04 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Toyota.
Doing intersite inbound replication test on site Chrysler:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site Chrysler is: DESTMX01.
Checking for down bridgeheads ...
Bridghead Mazda\MAZSERV01 is up and replicating fine.
*Warning: Remote bridgehead Chrysler\CHRSERV03 is not eligible
as a bridgehead due to too many failures. Replication may be
disrupted into the local site Chrysler.
Bridghead Mazda\MAZSERV02 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Bridghead Toyota\TOYSERV07 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead Hyundai\DESTVPN is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
Bridghead Toyota\TOYSERV06 is up and replicating fine.
Bridghead Chrysler\DESTMX01 is up and replicating fine.
Bridghead Honda\HONSERV02 is up and replicating fine.
*Warning: Remote bridgehead Chrysler\C-HOLDCOSRV02 is not
eligible as a bridgehead due to too many failures. Replication
may be disrupted into the local site Chrysler.
Bridghead Hastings\HH-SERV04 is up and replicating fine.
Doing in depth site analysis ...
Remote site Honda is replicating to the local site Chrysler the
writeable NC ForestDnsZones correctly.
Remote site Honda is replicating to the local site Chrysler the
writeable NC DomainDnsZones correctly.
Remote site Honda is replicating to the local site Chrysler the
writeable NC Schema correctly.
Remote site Honda is replicating to the local site Chrysler the
writeable NC Configuration correctly.
Remote site Honda is replicating to the local site Chrysler the
writeable NC azizco correctly.
Remote site Hyundai is replicating to the local site Chrysler
the writeable NC ForestDnsZones correctly.
Remote site Hyundai is replicating to the local site Chrysler
the writeable NC DomainDnsZones correctly.
Remote site Hyundai is replicating to the local site Chrysler
the writeable NC Schema correctly.
Remote site Hyundai is replicating to the local site Chrysler
the writeable NC Configuration correctly.
Remote site Hyundai is replicating to the local site Chrysler
the writeable NC azizco correctly.
Remote site Toyota is replicating to the local site Chrysler the
writeable NC ForestDnsZones correctly.
Remote site Toyota is replicating to the local site Chrysler the
writeable NC DomainDnsZones correctly.
Remote site Toyota is replicating to the local site Chrysler the
writeable NC Schema correctly.
Remote site Toyota is replicating to the local site Chrysler the
writeable NC Configuration correctly.
Remote site Toyota is replicating to the local site Chrysler the
writeable NC azizco correctly.
Remote site Mazda is replicating to the local site Chrysler the
writeable NC ForestDnsZones correctly.
Remote site Mazda is replicating to the local site Chrysler the
writeable NC DomainDnsZones correctly.
Remote site Mazda is replicating to the local site Chrysler the
writeable NC Schema correctly.
Remote site Mazda is replicating to the local site Chrysler the
writeable NC Configuration correctly.
Remote site Mazda is replicating to the local site Chrysler the
writeable NC azizco correctly.
Remote site Hastings is replicating to the local site Chrysler
the writeable NC ForestDnsZones correctly.
Remote site Hastings is replicating to the local site Chrysler
the writeable NC DomainDnsZones correctly.
Remote site Hastings is replicating to the local site Chrysler
the writeable NC Schema correctly.
Remote site Hastings is replicating to the local site Chrysler
the writeable NC Configuration correctly.
Remote site Hastings is replicating to the local site Chrysler
the writeable NC azizco correctly.
Remote site 4716 is replicating to the local site Chrysler the
writeable NC ForestDnsZones correctly.
Remote site 4716 is replicating to the local site Chrysler the
writeable NC DomainDnsZones correctly.
Remote site 4716 is replicating to the local site Chrysler the
writeable NC Schema correctly.
Remote site 4716 is replicating to the local site Chrysler the
writeable NC Configuration correctly.
Remote site 4716 is replicating to the local site Chrysler the
writeable NC azizco correctly.
Doing intersite inbound replication test on site Mazda:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site Mazda is: MAZSERV02.
Checking for down bridgeheads ...
Bridghead Chrysler\CHRSERV03 is up and replicating fine.
Bridghead Mazda\MAZSERV02 is up and replicating fine.
Bridghead Hyundai\DESTVPN is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
Bridghead Honda\HONSERV02 is up and replicating fine.
Bridghead Hyundai\HYUSERV02 is up and replicating fine.
Bridghead Toyota\TOYSERV07 is up and replicating fine.
Bridghead Chrysler\C-HOLDCOSRV02 is up and replicating fine.
Bridghead Hastings\HH-SERV04 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead Mazda\MAZSERV01 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Mazda.
Doing intersite inbound replication test on site Hastings:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site Hastings is: HH-SERV04.
Checking for down bridgeheads ...
Bridghead Toyota\TOYSERV06 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead Hyundai\DESTVPN is up and replicating fine.
Bridghead Mazda\MAZSERV02 is up and replicating fine.
Bridghead Chrysler\C-HOLDCOSRV02 is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
Bridghead Hastings\HH-SERV04 is up and replicating fine.
Bridghead Mazda\MAZSERV01 is up and replicating fine.
Bridghead Hyundai\HYUSERV02 is up and replicating fine.
Bridghead Chrysler\CHRSERV03 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Hastings.
Doing intersite inbound replication test on site 4716:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site 4716 is: HH-SERV05.
Checking for down bridgeheads ...
Bridghead Mazda\MAZSERV01 is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
Bridghead Mazda\MAZSERV02 is up and replicating fine.
Bridghead Hyundai\HYUSERV02 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead Chrysler\C-HOLDCOSRV02 is up and replicating fine.
Bridghead Toyota\TOYSERV07 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Bridghead Hyundai\DESTVPN is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
4716.
......................... azizco.com passed test IntersiteC:\Users\administrator.AZIZCO>
The Big Lug
-
Thursday, May 24, 2012 4:52 AMThe ISTG for site Mazda is: MAZSERV02.
Checking for down bridgeheads ...
Bridghead Chrysler\CHRSERV03 is up and replicating fine.
Bridghead Mazda\MAZSERV02 is up and replicating fine.
Bridghead Hyundai\DESTVPN is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
Bridghead Honda\HONSERV02 is up and replicating fine.
Bridghead Hyundai\HYUSERV02 is up and replicating fine.
Bridghead Toyota\TOYSERV07 is up and replicating fine.
Bridghead Chrysler\C-HOLDCOSRV02 is up and replicating fine.
Bridghead Hastings\HH-SERV04 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead Mazda\MAZSERV01 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Mazda.
Doing intersite inbound replication test on site Hastings:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site Hastings is: HH-SERV04.
Checking for down bridgeheads ...
Bridghead Toyota\TOYSERV06 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead Hyundai\DESTVPN is up and replicating fine.
Bridghead Mazda\MAZSERV02 is up and replicating fine.
Bridghead Chrysler\C-HOLDCOSRV02 is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
Bridghead Hastings\HH-SERV04 is up and replicating fine.
Bridghead Mazda\MAZSERV01 is up and replicating fine.
Bridghead Hyundai\HYUSERV02 is up and replicating fine.
Bridghead Chrysler\CHRSERV03 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Hastings.
Doing intersite inbound replication test on site 4716:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site 4716 is: HH-SERV05.
Checking for down bridgeheads ...
Bridghead Mazda\MAZSERV01 is up and replicating fine.
Bridghead 4716\HH-SERV05 is up and replicating fine.
Bridghead Mazda\MAZSERV02 is up and replicating fine.
Bridghead Hyundai\HYUSERV02 is up and replicating fine.
Bridghead Honda\HONSERVER01 is up and replicating fine.
Bridghead Chrysler\C-HOLDCOSRV02 is up and replicating fine.
Bridghead Toyota\TOYSERV07 is up and replicating fine.
Bridghead Hastings\HH-SERV03 is up and replicating fine.
Bridghead Hyundai\DESTVPN is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
4716.
......................... azizco.com passed test IntersiteThe Big Lug
-
Thursday, May 24, 2012 5:44 AM
In repadmin output you are getting the remote system is not available.Refer below link for the same.
http://support.microsoft.com/kb/2200187Also the A Good Time Server could not be located.The server holding the PDC role is down.Ensure authorative time server is configured correctly and PDC server is reachable.
Configure authorative time server on the PDC role holder server below is the KB article for the same.
http://support.microsoft.com/kb/816042Please also make sure that udp port 123 which as direction the chosen NTP server is not blocked.
Active Directory Firewall Ports requirement.
http://technet.microsoft.com/en-us/library/bb727063.aspxEnsure the following on DC:
1. Each DC / DNS server points to its private IP address as primary DNS server and other remote/local DNS servers as secondary in TCP/IP properties.
2. Each DC has just one IP address and single network adapter is enabled.
3. Contact your ISP and get valid DNS IPs from them and add it in to the forwarders, Do not set public DNS server in TCP/IP setting of DC.
4. Once you are done, run "ipconfig /flushdns & ipconfig /registerdns", restart DNS and NETLOGON service each DC.
Do not put private DNS IP addresses in forwarder list.
5.Assigning static IP address to DC if IP address is assigned by DHCP server to DC.It is strongly not recommended.Please use skydrive and post the log.
Best Regards,
Sandesh Dubey.
MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. -
Thursday, May 24, 2012 6:33 AM
Error - (1256) The remote system is not available , shows there is problem with name resolution, Did you check the DNS Configuration of DESTVPN and HONSERVER01?
Make sure that the DNS settings are proper on all the DC and restart the Netlogon services on them.Also on the DC make sure they are not multihomed,if any of the unused NIC's are there please have them disabled.
------------------------------------------------------------------------------------------------
DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is downThis error shows there is a problem in time sync in your domain. Did you run netdom query FSMO and checked the DC holding PDCEmulator is up and running?
Also I would recommend you to run W32tm /monitor to check the time synchronization in your DOmain
Ace has got good article on this. Please refer this
Regards,
_Prashant_
MCSA|MCITP SA|Microsoft Exchange 2003 Blog - http://prashant1987.wordpress.com Disclaimer: This posting is provided AS-IS with no warranties/guarantees and confers no rights.
-
Thursday, May 24, 2012 6:55 AM
Hello,
assure that firewals are not blocking traffic required for AD http://technet.microsoft.com/en-us/library/dd772723(v=ws.10).aspx
Please UPLOAD the following files to Windows sky drive so we get a complete overview:
ipconfig /all >c:\ipconfig.txt [from each DC/DNS Server]
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)]
dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)
As the output will become large, DON'T post them into the thread, please use Windows Sky Drive (skydrive.live.com) [with open access!] and add the link from it here. Also the /e in dcdiag scans the complete forest, so better run it on COB.
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
-
Thursday, May 24, 2012 4:57 PM
Hi:
I'm going to give some more background, just so i don't get some of you foing in the wrong direction. I have have the domain going for 8 years. started 2003 r2. I have upgraded all servers to 2008 or 2008r2, ith the exception of 1 2003 r2 server , which was my old exchange server and is a DC still. I probably should decommission it.
I added one site last July (site Mazda) and another in august. and one 2 weeks ago. these are the ones that are not showing up in "location". Repadmin /syncall and showrepl seldom comeup with issues (internet sometimes) so firewall is not an issue.
Doing other checks now
The Big Lug
-
Saturday, May 26, 2012 2:48 PMModerator
Hi BigLug,
How about the check results? Please update it for further assit if you need help.
Regards,
Cicely- Edited by Cicely FengMicrosoft Contingent Staff, Moderator Saturday, May 26, 2012 2:49 PM
-
Saturday, May 26, 2012 3:10 PM
Hi Cicely:
Update:
I have decommisioned the W2K03 server. The time issue is resolved. I want to be clear what the issue is, with an example. I go to add a printer on one of the 3 new sites. when the choice for Location (browse) the option for the current site is not there. just the original 4 sites show up. yet in Sites and services and U&C they are there, ADSI and so on.
Biglug
The Big Lug
-
Monday, May 28, 2012 6:12 AM
It seems that printer is not published in Active Directory hence you are not able to view the same.
To publish a printer in Active Directory
Open Printers and Faxes.
Right-click the printer you want to publish, and then click Sharing.
On the Sharing tab, click Share this printer, and then type a name for the shared printer.
Select the List in the Directory check box to publish the printer in Active Directory.
Reference link:http://technet.microsoft.com/en-us/library/cc737008(v=ws.10).aspxBest Regards,
Sandesh Dubey.
MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. -
Monday, May 28, 2012 8:23 AMModerator
Hi BigLug,
First, I want to clarify with you that did you mean the location value of new sites appeared in Sites and services after you decommissioned the W2K03 server? If yes, I think your original question has been resolved right? If no, please use repadmin /replsum to check again if there is any other issue between the current domain controllers.
Besides, I'm a little confused when you said "I go to add a printer on one of the 3 new sites. when the choice for Location (browse) the option for the current site is not there", could you please clarify it with us or provide some image to show how you get the site information when you added a printer? If you just can't add a printer, please try to share the printer before you add it as Sandesh suggested above.
Regards,
Cicely -
Monday, May 28, 2012 2:29 PM
Hi Cicely:
I was just saying that I decommisioned the 03 server.
replsum
Source DSA largest delta fails/total %% erro
C-HOLDCOSRV02 30m:00s 0 / 60 0
CHRSERV03 32m:50s 0 / 45 0
DESTVPN 35m:36s 0 / 45 0
HH-SERV03 28m:24s 0 / 40 0
HH-SERV04 28m:55s 0 / 20 0
HH-SERV05 14m:57s 0 / 55 0
HONSERV02 13m:39s 0 / 25 0
HONSERVER01 37m:21s 0 / 55 0
HYUSERV02 36m:20s 0 / 35 0
MAZSERV01 14m:56s 0 / 45 0
MAZSERV02 14m:56s 0 / 40 0
TOYSERV06 14m:56s 0 / 45 0
TOYSERV07 23m:13s 0 / 30 0
Destination DSA largest delta fails/total %% erro
C-HOLDCOSRV02 32m:50s 0 / 45 0
CHRSERV03 30m:03s 0 / 45 0
DESTVPN 36m:20s 0 / 40 0
HH-SERV03 28m:57s 0 / 30 0
HH-SERV04 28m:27s 0 / 35 0
HH-SERV05 13m:45s 0 / 40 0
HONSERV02 36m:06s 0 / 40 0
HONSERVER01 13m:32s 0 / 45 0
HYUSERV02 35m:37s 0 / 50 0
MAZSERV01 :37s 0 / 40 0
MAZSERV02 07m:20s 0 / 50 0
TOYSERV06 23m:16s 0 / 40 0The Big Lug
-
Tuesday, May 29, 2012 5:01 AMModerator
Hi,
According to this article: http://technet.microsoft.com/en-us/library/cc784120(v=ws.10).aspx, to enable printer location tracking, you must have a subnet object for each site. Could you please help to check if there is a subnet object with each new added site? If not, please use Active Directory Sites and Services to create them and after that try again. And also check and make sure your configuration could meet all conditions which printer location tracking requires listed in article.
In addition to, note that Locations defined for both Site and Subnet objects must follow the same location hierarchy used by printers published within Active Directory. If either the Site or Subnet object has a location field which does not match the hierarchy used by printers, the Find Printers dialog box will not function as expected.Regards,
Cicely -
Tuesday, May 29, 2012 4:01 PM
that was already set correctly, as far as printers go.
This is from sites and services
The Big Lug
-
Tuesday, May 29, 2012 4:28 PMhttps://profile.live.com/cid-3d6983a142f027de/#!https://skydrive.live.com/?cid=3d6983a142f027de&group=0&sc=documents!cid=3D6983A1https://profile.live.com/cid-3d6983ahttps://profile.live.com/cid-3d6983a142f027de/#!https://skydrive.live.com/?cid=3d6983a142f027de&group=0&sc=documents!cid=3D6983A142F027DE&id=3D6983A142F027DE%21122&sc=documents142f027de/#!https://skydrive.live.com/?cid=3d6983a142f027de&group=0&sc=documents!cid=3D6983A142F027DE&id=3D6983A142F027DE%
The Big Lug
-
Tuesday, May 29, 2012 4:52 PM
Hello,
even with deviding the link-chaos into links starting with https there is no option to open anything. So please add the links again and DEVIDE them BEFORE posting.
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
-
Tuesday, May 29, 2012 4:58 PM
-
Thursday, May 31, 2012 2:24 PM
Hi,
Replication latency/errors should not be the cause of our issue.
i notice the "location" you mentioned is a subnet object, rather than a site object. If you add a description to each subnet object, will it be shown up in the "location"?
Regards,
Denny
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.
-
Tuesday, June 05, 2012 8:33 PM
Hi:
Done that. No worky.. but thanks..
The Big Lug
-
Friday, June 22, 2012 3:51 PM
Meinolf Weber:
Any ideas?
The Big Lug
-
Wednesday, August 22, 2012 7:39 PMAfter everthing. i went into the schema mgmt and updated the properties.
The Big Lug
.png)
