Is a controller required for roaming?

We've been using single stand-alone Aironet AP's at our small branch offices with great reliability and success over the last 3 years.  However, we recently acquired an office with only a few clients (10), but it is an old warehouse so it has a lot of square footage so multiple AP's will be needed to cover the area.
If I go with 6 1600 AP's do I have to use a controller (such as 2500) for clients to be able to automatically roam between the AP's as they walk throughout the warehouse with their laptops, or can I just use the stand-alone AP's instead that I'm accustomed to?
Thanks for the help!

around 20% overlap is ideal; correct?
That's correct.  20% would be ideal.  That's voice-quality recommendation.  If you get your autonomous wireless set up for voice-quality, then you've got it made.
Also, are there any advantages to lightweight vs autonomous in regards to roaming, such as quicker handoff or something similar due to the controller?
Just make sure you update the firmware of your wireless NIC.  This seems to be the greatest angst among people.

Similar Messages

  • ISSUE: "This domain controller must register a DNS SRV resource record, which is required for replication to function correctly"

    so we currently have three domain controllers set up, two of them on 2012r2 and one of them on 2008r2. prior to any of these domain controllers being added to the domain there was only one, running on 2003r2. the 2003r2 server was up and running when the
    first 2012r2 was added and that's when running 'dcdiag /e /c /v' would yield an issue with "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local" in the DNS portion of the diagnostics, specifically:
    TEST: Records registration (RReg)
    Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
    Error:
    Missing SRV record at DNS server 192.168.22.4:
    _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
    after adding the second 2012r2 to the domain, this issue is still there... adding the 2008r2 server to the domain and running BPA it gives the following:
    Title:
    This domain controller must register a DNS SRV resource record, which is required for replication to function correctly
    Severity:
    Error
    Date:
    7/3/2014 11:24:48 AM
    Category:
    Configuration
    Issue:
    The "DcByGuid" DNS service (SRV) resource record that advertises this server as an available domain controller in the domain and ensures correct replication is not registered. All domain controllers (but not RODCs) in the domain must register this record.
    Impact:
    Other member computers and domain controllers in the domain or forest will not be able to locate this domain controller. This domain controller will not be able to provide a full suite of services.
    Resolution:
    Ensure that "DcByGuid" is not configured in the "DnsAvoidRegisteredRecords" list, either through Group Policy or through the registry. Restart the Netlogon service. Verify that the DNS service (SRV) resource record "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local", pointing to the local domain controller "CM-DC4-NY01.cmedia.local", is registered in DNS.
    More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=126968
    I've tried scanning and then re-scanning every single entry in DNS Manager and do not see any reference to this specific GUID mentioned, nor do I see any other domain controllers referenced that should not be in there. The two 2012r2 and the 2008r2 domain
    controllers are the only ones listed in DNS Manager... the 2003r2 mentioned earlier failed and was removed.

    Just to chime in, I noticed that you said you have one 2008 R2 DC, and two 2012 DCs.
    I also noticed in the ipconfig /all that all DCs are pointint to themselves for DNS. We usually like to see them point to a partner, then itslelf as the second entry, w hether loopback or by its own IP.
    Based on that, what I suggest to level the playing field by choosing the WIndows 2008 R2 DC as the first DNS on all DCs and only administer DNS using that DC. The reason I chose that is because of the least common denominator is what we rather use so we
    don't invoke any new features in the newer 2012 DNS console that 2008 R2 may not understand.  After that's done, on each DC run (and you can use a PowerShell window to run this):
    Rename the system32\config\netlogon.dns and netlogon.dnb files by suffixing ".old" to the file.
    ipconfig /registerdns
    net stop netlogon
    net start netlogon
    Then re-run the dcdiag /e /c /v.
    Post your results, please.
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.
    I thought the DNS entries were supposed to be the other way around? point to themselves first and a partner as secondary? regardless, as requested, I've changed it to what you've prescribed where they point to the 2008r2 server as the primary with themselves
    as the secondary. I've also followed the steps to what seems like refreshing the DNS? on each of the DCs. Here's the output from dcdiag /e /c /v
    Directory Server Diagnosis
    Performing initial setup:
    Trying to find home server...
    * Verifying that the local machine CM-DC1-NY01, is a Directory Server.
    Home Server = CM-DC1-NY01
    * Connecting to directory service on server CM-DC1-NY01.
    * Identified AD Forest.
    Collecting AD specific global data
    * Collecting site info.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory
    =ntDSSiteSettings),.......
    The previous call succeeded
    Iterating through the sites
    Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia
    ,DC=local
    Getting ISTG and options for the site
    * Identifying all servers.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=nt
    DSDsa),.......
    The previous call succeeded....
    The previous call succeeded
    Iterating through the list of servers
    Getting information for the server CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    * Identifying all NC cross-refs.
    * Found 3 DC(s). Testing 3 of them.
    Done gathering initial info.
    Doing initial required tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC1-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC3-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC4-NY01 passed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Advertising
    The DC CM-DC1-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC1-NY01 is advertising as an LDAP server
    The DC CM-DC1-NY01 is advertising as having a writeable directory
    The DC CM-DC1-NY01 is advertising as a Key Distribution Center
    The DC CM-DC1-NY01 is advertising as a time server
    The DS CM-DC1-NY01 is advertising as a GC.
    ......................... CM-DC1-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    [CM-DC1-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC1-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC1-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC1-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC1-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC1-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    ......................... CM-DC1-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC1-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC1-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC1-NY01\netlogon
    Verified share \\CM-DC1-NY01\sysvol
    ......................... CM-DC1-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC1-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC1-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC1-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC1-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 4609 to 5108
    * rIDPreviousAllocationPool is 4609 to 5108
    * rIDNextRID: 4629
    ......................... CM-DC1-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC1-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    A warning event occurred. EventID: 0x0000002F
    Time Generated: 07/08/2014 13:19:14
    Event String:
    Time Provider NtpClient: No valid response has been received from manually configured peer 0.ca.pool.ntp.org
    after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a n
    ew peer with this DNS name. The error was: The peer is unreachable.
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC1-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC1-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC1-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC1-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Advertising
    The DC CM-DC3-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC3-NY01 is advertising as an LDAP server
    The DC CM-DC3-NY01 is advertising as having a writeable directory
    The DC CM-DC3-NY01 is advertising as a Key Distribution Center
    The DC CM-DC3-NY01 is advertising as a time server
    The DS CM-DC3-NY01 is advertising as a GC.
    ......................... CM-DC3-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC3-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC3-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC3-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC3-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC3-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC3-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC3-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    ......................... CM-DC3-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC3-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC3-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC3-NY01\netlogon
    Verified share \\CM-DC3-NY01\sysvol
    ......................... CM-DC3-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC3-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC3-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC3-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC3-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15109 to 15608
    * rIDPreviousAllocationPool is 15109 to 15608
    * rIDNextRID: 15110
    ......................... CM-DC3-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC3-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC3-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC3-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC3-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC3-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Advertising
    The DC CM-DC4-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC4-NY01 is advertising as an LDAP server
    The DC CM-DC4-NY01 is advertising as having a writeable directory
    The DC CM-DC4-NY01 is advertising as a Key Distribution Center
    The DC CM-DC4-NY01 is advertising as a time server
    The DS CM-DC4-NY01 is advertising as a GC.
    ......................... CM-DC4-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC4-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC4-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC4-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC4-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC4-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC4-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC4-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    ......................... CM-DC4-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC4-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC4-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC4-NY01\netlogon
    Verified share \\CM-DC4-NY01\sysvol
    ......................... CM-DC4-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC4-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC4-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC4-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC4-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15609 to 16108
    * rIDPreviousAllocationPool is 15609 to 16108
    * rIDNextRID: 15609
    ......................... CM-DC4-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC4-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC4-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC4-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC4-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC4-NY01 passed test VerifyReplicas

  • Hardware Requirements for a Windows Server 2012 Domain Controller.

    Hi,
    I have a secondary office with 10 users with a domain controller that has reached its end of life.  We like to upgrade the current hardware to serve as a domain controller and potentially as an onsite file server that will sync with head office during
    off peak business hours.
    Any recommendations for a low cost yet reliable hardware for the above solution ?

    Hi,
    Thanks for your post.
    I think you need to meet the requirement for upgrading to windows server 2012r2.
    http://technet.microsoft.com/en-us/library/hh994618.aspx#BKMK_SysReqs
    And you could refer to the following article about windows server 2012r2 domain controller configuration
    Building Your First Domain Controller on 2012 R2
    http://social.technet.microsoft.com/wiki/contents/articles/22622.building-your-first-domain-controller-on-2012-r2.aspx
    Regards.
    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]

  • Controller failover for different controllers

    Hi,
    I have 3 existing controller with different model, capacity, version and configurations. I have purchased new controller that supports 100 APs.
    Let's say WLC_A has a capacity of 25 APs and caters 20 APs, WLC_B has a capacity of 12 APs and caters 12APs, WLC_C has a capcity of 50 and caters 30APs. the NEW WLC, WLC_NEW has a capacity of 100 and will only have 18 APs registered to it.
    What will be the requirement for me to have WLC_A, WLC_B, WLC_C failover to WLC_NEW, given that all OLD WLCs have different version and configurations? We are trying to make this as HA as possible.

    Let me try to explain this a little better.  If you have the following like you posted earlier and all these WLC's are located in the same building and you mobility between the two.  When a user roams from one WLC to another, it will break and the user will have a hard time accessing the SSID.  This is because you changed the security method.  You can't apply multiple security profiles on a client.
    WLC_A
    SSID: Guest
    Security: none
    VLAN: 20 SW_A
    WLC_B
    SSID:Guest
    Security:web auth
    VLAN: 40 SW_B
    WLC_NEW
    SSID:Guest
    Security:WPA_PSK
    VLAN: 20 SW_NEW
    What you need to do is define your wireless requirements (SSID & Security method)  You want to have the same SSID have the same security method and preferably have the dynamic interfaces on the same subnet if your L2 to the access.
    This is how you should have guest as an example.  All the WLC should be in the same mobility group!
    WLC_A
    SSID: Guest
    Security: WebAuth
    VLAN: 20 SW_A
    10.20.10.20/24
    WLC_B
    SSID:Guest
    Security:WebAuth
    VLAN: 20 SW_B
    10.20.10.21
    WLC_NEW
    SSID:Guest
    Security:WebAuth
    VLAN: 20 SW_NEW
    10.20.10.22
    This setup will allow users to roam from one WLC to another seamlessly.

  • Creating Planned orders and Requisitions for a particular MRP controller and for all the others only Requisition is to be created.

    Hi Experts,
    Currently we run Program 'RMMRP000' as a batch job to create Planned orders and requisitions.
    The client wants that Planned orders and Requisitions should be created for a particular MRP controller and for all the others only Requisition is to be created.
    I implemented Exit 'EXIT_SAPMM61X_001' in the following manner by passing MRP controller to user_key.
      IF mt61d-dispo <> user_key.
        no_planning = 'X'.
      ENDIF.
    But as you can see that this will not meet my client requirement.
    If any of you has worked on similar requirement / if any one knows that this is achievable or not,
    please share your inputs.

    Moved from SAP ERP Sales and Distribution (SAP SD) to ABAP Development
    G. Lakshmipathi

  • Max IPs in a DHCP range for Roaming network?

    Setting up an AirPort roaming network comprised of a dozen or so AirPort-Extremes all connected via a Fast Ethernet backbone.
    The Master base station has a Public IP on it's WAN side and is Set to 'Share a Public IP address' and DHCP - but it seems no matter which network prefix I choose for the LAN side, I can not create a DHCP range larger than a single Class C. Is there a way to give out more than 254 IPs? Or can you have a single roaming network with multiple base stations set to DHCP?

    Is there a way to give out more than 254 IPs?
    No, as the "main" router, providing DHCP server service is the limiting factor here.
    Or can you have a single roaming network with multiple base stations set to DHCP?
    This may be possible, but NOT with the Apple routers. When configured as bridges, as required for a roaming network, both their NAT & DHCP services are disabled.

  • Which files are require for sap IDES ecc6.0 ehp6 with windows 2008 and db2 LUW 10.1

    Hi professionals,
    Please help me out which file are require to download for SAP IDES ecc6.0 ehp6 with windows 2008 and db2 LUW 10.1
    My requirement is to install Windows2008 R2 Service pack 1 + ECC6.0 ehp6 + DB2 LUW
    So according to this i found these files,please tell me which one i require. second thing i am not able to find instalation master DVD in it.So which file is best for my environment.
    51044815_1           BD IDES SAP ERP 6.0 EHP6 Inst. Export 1 of 40
    51041991_1                 BS2011 Java Components - NW 7.03 1 of 4
      51041992                SAP ERP 6.0 EHP6 Components
    51041988_6                 NW703 UC-Kernel 720_EXT Windows Server on x64 64bit
    51041988_5
    NW703 Kernel 720_EXT Windows Server on x64 64bit
    51041988_7
    SL CONTROLLER 700
    51041988_8
    SL CONTROLLER 720
    51041991_1
    BS2011 Java Components - NW 7.03 1 of 4
    51048277_3
    721 NUC Kernel for SWPM SP06 - Windows Server on x64 64bit
    51048277_6
    721 UC Kernel for SWPM SP06 - Windows Server on x64 64bit
    51048277_7
    SL CONTROLLER 700 for SWPM SP06
    51048277_8
    SL CONTROLLER 721 for SWPM SP06
    51048285_2
    721_EXT NUC Kernel for SWPM SP06 - Windows Server x64 64bit
    51048285_4
    721_EXT UC Kernel for SWPM SP06 - Windows Server x64 64bit
    51048285_5
    SL CONTROLLER 700 for SWPM SP06
    51048285_6
    SL CONTROLLER 721 for SWPM SP06
    51048532
    DB2 LUW 10.1 FP4 RDBMS Windows x64
    51048533
    DB2 LUW 10.1 FP4 RDBMS CLI/JDBC-Driver
    51041988_9
    DB2 USER ENV
    51041988_11
    DB6 USER ENV
    51041988_10
    DB4 USER ENV
    Thanks & Regards,
    Bhipra Sakti

    Hi Bhipra,
    You need below DVDs for ERP 6.0 EHP6 IDES
    51041985_11
    DB2 USER ENV
    70SWPM10SP06_4-20009707.sar
    70SWPM10SP06
    51044815_1
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 1 of 40
    51044815_10
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 10 of 40
    51044815_11
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 11 of 40
    51044815_12
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 12 of 40
    51044815_13
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 13 of 40
    51044815_14
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 14 of 40
    51044815_15
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 15 of 40
    51044815_16
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 16 of 40
    51044815_17
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 17 of 40
    51044815_18
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 18 of 40
    51044815_19
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 19 of 40
    51044815_2
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 2 of 40
    51044815_20
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 20 of 40
    51044815_21
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 21 of 40
    51044815_22
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 22 of 40
    51044815_23
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 23 of 40
    51044815_24
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 24 of 40
    51044815_25
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 25 of 40
    51044815_26
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 26 of 40
    51044815_27
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 27 of 40
    51044815_28
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 28 of 40
    51044815_29
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 29 of 40
    51044815_3
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 3 of 40
    51044815_30
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 30 of 40
    51044815_31
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 31 of 40
    51044815_32
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 32 of 40
    51044815_33
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 33 of 40
    51044815_34
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 34 of 40
    51044815_35
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 35 of 40
    51044815_36
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 36 of 40
    51044815_37
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 37 of 40
    51044815_38
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 38 of 40
    51044815_39
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 39 of 40
    51044815_4
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 4 of 40
    51044815_40
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 40 of 40
    51044815_5
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 5 of 40
    51044815_6
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 6 of 40
    51044815_7
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 7 of 40
    51044815_8
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 8 of 40
    51044815_9
    BD IDES SAP ERP 6.0 EHP6 Inst. Export 9 of 40
    51048277_6
    721 UC Kernel for SWPM SP06 - Windows Server on x64 64bit
    51048277_8
    SL CONTROLLER 721 for SWPM SP06
    51048532
    DB2 LUW 10.1 FP4 RDBMS Windows x64
    51048533
    DB2 LUW 10.1 FP4 RDBMS CLI/JDBC-Driver
    Hope this helps.
    Regards,
    Deepak Kori

  • Which file are require for sap IDES ecc6.0 ehp6 with windows 2008 and db2 LUW 10.1

    Hi professionals,
    Please help me out which file are require to download for SAP IDES ecc6.0 ehp6 with windows 2008 and db2 LUW 10.1
    My requirement is to install Windows2008 R2 Service pack 1 + ECC6.0 ehp6 + DB2 LUW
    So according to this i found these files,please tell me which one i require. second thing i am not able to find instalation master DVD in it.So which file is best for my environment.
    51044815_1           BD IDES SAP ERP 6.0 EHP6 Inst. Export 1 of 40
    51041991_1                 BS2011 Java Components - NW 7.03 1 of 4
      51041992                SAP ERP 6.0 EHP6 Components
    51041988_6                 NW703 UC-Kernel 720_EXT Windows Server on x64 64bit
    51041988_5
    NW703 Kernel 720_EXT Windows Server on x64 64bit
    51041988_7
    SL CONTROLLER 700
    51041988_8
    SL CONTROLLER 720
    51041991_1
    BS2011 Java Components - NW 7.03 1 of 4
    51048277_3
    721 NUC Kernel for SWPM SP06 - Windows Server on x64 64bit
    51048277_6
    721 UC Kernel for SWPM SP06 - Windows Server on x64 64bit
    51048277_7
    SL CONTROLLER 700 for SWPM SP06
    51048277_8
    SL CONTROLLER 721 for SWPM SP06
    51048285_2
    721_EXT NUC Kernel for SWPM SP06 - Windows Server x64 64bit
    51048285_4
    721_EXT UC Kernel for SWPM SP06 - Windows Server x64 64bit
    51048285_5
    SL CONTROLLER 700 for SWPM SP06
    51048285_6
    SL CONTROLLER 721 for SWPM SP06
    51048532
    DB2 LUW 10.1 FP4 RDBMS Windows x64
    51048533
    DB2 LUW 10.1 FP4 RDBMS CLI/JDBC-Driver
    51041988_9
    DB2 USER ENV
    51041988_11
    DB6 USER ENV
    51041988_10
    DB4 USER ENV
    Thanks & Regards,
    Bhipra Sakti

    Hi professionals,
    Please help me out which file are require to download for SAP IDES ecc6.0 ehp6 with windows 2008 and db2 LUW 10.1
    My requirement is to install Windows2008 R2 Service pack 1 + ECC6.0 ehp6 + DB2 LUW
    So according to this i found these files,please tell me which one i require. second thing i am not able to find instalation master DVD in it.So which file is best for my environment.
    51044815_1           BD IDES SAP ERP 6.0 EHP6 Inst. Export 1 of 40
    51041991_1                 BS2011 Java Components - NW 7.03 1 of 4
      51041992                SAP ERP 6.0 EHP6 Components
    51041988_6                 NW703 UC-Kernel 720_EXT Windows Server on x64 64bit
    51041988_5
    NW703 Kernel 720_EXT Windows Server on x64 64bit
    51041988_7
    SL CONTROLLER 700
    51041988_8
    SL CONTROLLER 720
    51041991_1
    BS2011 Java Components - NW 7.03 1 of 4
    51048277_3
    721 NUC Kernel for SWPM SP06 - Windows Server on x64 64bit
    51048277_6
    721 UC Kernel for SWPM SP06 - Windows Server on x64 64bit
    51048277_7
    SL CONTROLLER 700 for SWPM SP06
    51048277_8
    SL CONTROLLER 721 for SWPM SP06
    51048285_2
    721_EXT NUC Kernel for SWPM SP06 - Windows Server x64 64bit
    51048285_4
    721_EXT UC Kernel for SWPM SP06 - Windows Server x64 64bit
    51048285_5
    SL CONTROLLER 700 for SWPM SP06
    51048285_6
    SL CONTROLLER 721 for SWPM SP06
    51048532
    DB2 LUW 10.1 FP4 RDBMS Windows x64
    51048533
    DB2 LUW 10.1 FP4 RDBMS CLI/JDBC-Driver
    51041988_9
    DB2 USER ENV
    51041988_11
    DB6 USER ENV
    51041988_10
    DB4 USER ENV
    Thanks & Regards,
    Bhipra Sakti

  • Requirements for Desktop PCs as LabVIEW Real-Time Targets

    Hello
    I have read the Requirements for Desktop PCs as LabVIEW Real-Time Targets
    http://www.ni.com/white-paper/8239/en/
    and i have 2 questions:
    Supported Ethernet Chipsets:   Is Intel® i210AT Controller supported?
    Supported Processors: Is E3 and E5 Xeon Supported?
    thank you

    Dear goltnum9,
    Here some Whitepapers where you can read which Requirements must be given and also how do convert.
    Requirements for Desktop PCs as LabVIEW Real-Time Targets
    How do I Create a Desktop Real-Time System?
    Kind Regards,
    SG3 | Applications Engineering | National Instruments | NIG |

  • Requirements for AD integration

    Hey All,
    Trying to integrate AD into my MAC server environment and Im having some issues around adding my MAC server into the domain.
    I keep getting the error 5200 (Server could not be contacted.
    I have tried almost every suggestion from placing the OU where I want to add my MAC domain objects, to directory editor to format of the domain?
    Anyway I need to understand what type of account is the MAC looking for? I know DNS is configured correctly, I know the accounts I have used are domain admin and I have tried using the userPrincipleName as well as Domain\user format....
    At this point the guides are useless to me so any help is really appreciated.
    Thanks
    Steve

    Running dcpromo usually is enough as long as you are also running DNS off the windows controller.  For environments with both platforms it is generally better to keep AD as the center of the environment.  Then connect the Macs to AD.  But, DNS is critical.  Your windows server should be the one running DNS.  The DNS service on the Mac is not required.  All Macs should be getting DNS information from the Windows box because it will have all the SRV records in place.  This is for GC, LDAP, Kerberos, etc.  The next item is time.  Once again, Windows servers generally start time services automatically on the DC.  Point your Macs at the Windows machine to make sure the time is in sync.
    It sounds like you have everything in place.  The
    On your Mac Server, if you run this:
    sudo changeip -checkhostname
    What result do you get?  Then confirm all of the SRV records are in place on the DC.  Run these from your Mac.
    host -t SRV _kerberos._tcp.supergino.com
    host -t SRV _kerberos._udp.supergino.com
    host -t SRV _kpasswd._tcp.supergino.com
    host -t SRV _kpasswd._udp.supergino.com
    host -t SRV _gc._tcp.supergino.com
    host -t SRV _ldap._tcp.supergino.com
    Next, you can run Open Directory in debug mode to get more details of what is going on.  Use the odutil command to increase the log level to debug and then attempt a bind again.  Review the log output to see where the error is occurring.
    Generally speaking, when a Windows environment is using a TLD other than .local and all devices are agreeing on DNS and time, the AD bind is cake. 

  • Report showing independent requirements for several materials

    Hi
    Workiing in SAP 4.7
    Looking for a report where I can see independent requirements over time,  for several materials, based on a time characteristic such as month/week. So for example I want to see the independent requirements for 10 different materials in a list, with the time characteristic on the horizontal axis.
    Is there any such report? I am NOT asking for MD05/MD06/MD61/MD62.
    Thanks in advance,
    Lars
    Edited by: Lars Tornblom on Apr 27, 2011 10:09 AM

    Check in MD73
    if you are using requirement plan then check based on requirement plan else check based on MRP controller by giving period

  • Umi 7774 required for ni drives?

    i am designing a motion control system using 3 stepper motors (ni Nema 23) and correspondingly 3 ni P70360 drives. Is a umi 7774 required to connect these to the 4 axes pci motion controller card?  (i'm confused as its description on the ni site says that it is required for 3rd party drives BUT in the discussions i've read a lot of people have used umi 7774 with ni drives )
    Solved!
    Go to Solution.

    Hello aks, 
    Yes, you will need to purchase and use our Universal Motion Interface (UMI) 7774 board in order to connect the three drives/motors to the motion controller card. 
    It may have been confusing because we do explicitly say that it is required for 3rd party drives, but not necessarily required for our drives. Having said that, the vast majority of customers use the UMI board because it eliminates the need for custom cables, and makes it far easier to connect to more than one axis. 
    Here are some links that may provide more detail and could prove to be helpful.
    [1] NI Stepper Motion System Selection Guide
    [2] Cabling for a Motion System with a Danaher Drive Explained
    Huntington W
    National Instruments
    Applications Engineer
    ***Don't forget to give Kudos and Accepted as Solution where it is deserved***

  • What kind of network required for SMS?

    Hi everybody, I have a question concerning SMS:
    I travel a lot, and SMS is THE way of keeping communication affordable, and it normally works via the normal mobile network incurring just limited charges.
    Just now I read somewhere between the lines of some posts, that the iphone needs the EDGE-network for SMSing. That would be a huge disappointment, probably able to keep me from buying the phone, as it would mean that
    1. in countries with no EDGE network there's no SMS using the iphone at all
    2. in foreign countries where there is, it would require data roaming, causing significant charges, making an SMS pointless.
    Can anyone please confirm true or false?
    Thanks!

    What you have been told is simply not true: SMS is a voice—rather than data—service and standard voice plans support the transmission and reception of short message service messages across most carrier networks. You do not need an optional data plan or access to a data medium such as EDGE to send and receive these messages.
    Some plans bundle a defined number of transmissions and receptions into a monthly voice plan fee. Options for additional included SMS messages or unlimited messaging are widely available.

  • Authorizations  required for applying support packs

    What authorizations do you require for applying support packs?

    After u successfully downloaded the support pack from the service market place , the 1st authorization u need is for using the client 000.
    Only with the client 000 u will be available to import the support pack (ABAP suppotr package) using transaction SPAM. To use all SPAM functions, you require the following authorizations:
    S_TRANSPRT
    S_CTS_ADMIN
    If you log on in client 000, then your user master data contains the corresponding authorizations (inside the authorization profile) and you can use all the functions in Support Package Manager.
    For Java u can use jspm tool for applying the support packages for any component and if u want to enhance or upgrade the java components( say from ESS 1.1 to ESS 1.2) then u can do it using sdm tool.
    Before applying the pack u need to unpack the abap/java files using the commands in the command- prompt and copy the unpacked files into sap/sid/trans/eps/in folders of ur system.
    Also before using the SPAM for abap support pack make sure that u had set ur system as the domain-controller in transaction stms with ddic user and masterpwd.
    Go thru this document:-
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7a2e4346-0a01-0010-718a-fa846ad19716
    Award points if found helpful

  • SMTP Security for Roaming Users

    Hi all,
    We used to arrange our mobile users to use VPN to access our MS (2005Q4) server so that they can use it as a relay to send mail to external email addresses when they are roaming. The server is configured so it allows mail relay from internal (VPN) IP addresses so that it still protects us from external spammers from using it as an open relay.
    That works well for some time. However, it has 2 disadvanges:
    1. Users must first setup setup a VPN before getting mail, and that's a support nightmare
    2. Sending email this way allows any internal and VPN users to forge sender envelop address
    So I'm thinking the following:
    1. Enable SMTPS (to avoid the VPN stuff)
    2. Configure MS to require authentication for both SMTP and SMTPS for senders who uses @ourdomain.com email address in the envelop. And at the same time, match that envelop sender address with the authenticated user to see if they match.
    I have already done point #1. But #2 seems so complicated. Please advice if I am thinking in the correct direction. Is there a simpler way to archieve that?
    Any ideas are welcome.
    Thanks.
    BR,
    Py

    Hi,
    SMTPS is definitely a good idea for roaming users. If you are going to be requiring authentication then you want the authentication details to be encrypted.
    2. Configure MS to require authentication for both SMTP and SMTPS for senders who uses @ourdomain.com email address in the envelop. And at the same time, match that envelop sender address with the authenticated user to see if they match.This seems complex to me and is going to cause issues for users who send emails via their ISP's server to your work-place when working from home. Requiring authentication for the SMTPS connection is a good idea and that can be accomplished just by associating the TLS port with the SMTP_SUBMIT service (instead of just SMTP):
    [SERVICE=SMTP_SUBMIT]
    PORT=587
    ! Uncomment the following line if you want to support SSL on the alternate
    ! port 465
    TLS_PORT=465
    You should also enable the logging of the username used when authenticating by adding the following line to the option.dat file:
    LOG_USERNAME=1
    That way if there is a user who 'spoofs' their email address, you know who they are (by the username), the IP address they came from and who they were pretending to be. This should act as sufficient deterrent.
    Shane.

Maybe you are looking for