Refreshing the DEV system, which is our domain controller

Hi,
We refreshed our DEV system, which is our domain controller. How to get back our STMS configuration in the domain controller ? Can I run se06 in our proudction system to delete the TMS and then running STMS in production to create the TMS. Then approving that in the domain controller. Is there any other way to restore the configuration ?
Thanks
Rabi

You could always specify a backup domain controller before you start.

Similar Messages

  • Need to delete Transport system , which is not domain controller

    I need to delete transport system on machine which is not domain controller .
    our domain controller system is not avalible now .
    how can i delete the transport system on my machine as domain controller system is not avaliable .
    Please let me know what can i do ??
    Thanks,
    Asc

    Hi,
    Logon to any system which is in your transport path in client 000. Then in stms, go to Overview ---> Systems. Here you can find all the systems in your transport path. You can also find the domain controller which you have configured as before.
    Now, goto Extras----> Delete TMS Configuration.
    After deleting, logon to system which you want to make as domain controller in client 000. when you execute stms, now it will ask for new stms setup, which you might be aware of.
    If you need more guidance, let me know.
    Thanks,
    Sailesh K

  • Why development system is considered as domain controller ???

    Hi ,
    SAP recommends Production system as domain controller .Resaon is PRD is secured and has more availability.
    But ,Most of the customer systems development system is set as Domail controller.
    My guess on this point is , Development system will get installed fisrt in landscape and while configuring the STMS we have to use this system as domain controller.Later this scenario is not changed.
    Please let me know why development system is set as domain controller. I have see most of the customer systems are having DEV as domain controller. That's why I would like to know about this point.
    Thanks in advance.
    Venkat

    Hi
    To be specific, few clients do it, thinking of failover case. If your PRD system fails for some reason, it would effect the whole transport system if it is the domain controller.
    While if they make DEV or QA as domain controller, this can be ruled out.
    Again for QA, since it is assumed to be a copy of PRD system, and regularly experiences System refresh with PRD data, which would result in QA downtime, regularly. Which again is undesirable for a working transport system.
    So, inspite of recommendation by SAP for PRD system as domain controller, client goes for DEV system as domain controller.
    Hope this clarifies your question.
    Regards
    Rahul

  • Windows Server 2012 Foundation, in a Workgroup - "The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller"...

    Every few days we see two dialogs with the following messages:
    Dialog 1, title: Check for Licensing Compliance is Incomplete
    The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller.
    Dialog 2, title: Check for Licensing Compliance is Incomplete
    The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliance check cannot be completed, the server will automatically shut
    down in 8 day(s) 23 hour(s) 0 minute(s).
    The server is not (and never has been) joined to a domain or had any DC roles installed. In fact its still connected to the default Workgroup.
    The server was configured in our office and never showed this message until it was installed on site. The main difference from what I can see is that when installed on site it was given a static IP address and does not have any DNS settings in the network
    adapter properties. 
    I have scoured a number of forums on this error but in almost every other instance of this error message the servers are connected to a Domain Controller and the solutions generally are linked to dis-joining and rejoining the domain. Unfortunately this is
    not an option for this scenario.
    I initially thought that adding some relevant DNS server IP address may resolve the issue, however, we have the exact same model server configured exactly the same running at a different site that does not experience this problem. This server also has no
    DNS server configured.
    I have seen a post that suggests turning off the servers "Foundation Checking", but I'm unsure how to do this.

    Thanks for your response Vivian.
    I can confirm that this server is not (and never has been) a member of any active directory, it is configured as a Workgroup server. It was initially configured on a network that does have an active directory, but was never joined to it. During that time it
    never displayed these messages.
    The server was moved into production on a different site and network and setup with a static IP address.The site network does have its own active directory but the server was not joined to it. It is whilst on this new network that these messages began.
    Since my original post DNS servers have been added and the Microsoft activation has been verified, however, the messages are still appearing.
    There are only 2 user accounts configured on this server. The local admin account and another local admin user.
    The remote desktop services roles have been installed but not yet configured. I don't think that has any bearing on this scenario though.
    The description of this error in the above "Introduction to Windows Server 2012 Foundation" link states:
    This error occurs when the server cannot finish checking the requirements for the root domain, forest trust configuration, or both. It usually happens when the server cannot connect to a domain controller. If the situation persists, the server will
    shut down 10 days after the first time the compliance check failed. Each time this error message occurs, it will state the actual time remaining before the server will shut down. If you restart the server after it has shut down because of non-compliance, the
    server will shut itself down again in 3 days.
    The above description leads me to the following question - In a Workgroup environment, does the server still try to contact a domain controller to establish a level of trust? If this is the case could it be that the server can no longer see the initial DC
    on its new network and this is what is triggering the messages?
    Am I clutching at straws here?

  • Error determining whether the target server is already a domain controller: Failed to open the runspace pool

    Hi there , i already have some others DC running w2k12 R2 on the env, but when i was promoting another new DC running w2k12 R2 on the middle of the AD sync , the server encounter an error and rebooted it self ; after the server came back online , it keep
    saying that a configuration is required for AD Domain Services , like the step when you are about to promote the server , but when you try to promote it , the error "Error determining whether the target server is already a domain controller: Failed
    to open the runspace pool. The server manager winrm plug-in might be corrupted or missing."

    Hi,
    Thanks for your post.
    Please waitting for the replication is finished and rerun the domain prep command  to check the result.
    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]

  • Integration a web system which had window domain validation to EP7.0

    I have a EP7.0 system which on AIX ,another web system which on win2000,and when you access the web system,you had to access a windows domain Authentication,how I can implement the oss for them?

    Hi,
    check out the Document <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/47d0cd90-0201-0010-4c86-f81b1c812e50">Using SAP Logon Tickets for Single Sign on
    to Microsoft based web applications</a>.
    Best regards,
    Martin

  • How to recover/refresh the discovery system if system crashed.

    Hi,
    Can someone tell me how to recover the Discovery Sysm if the system crashed? Any recovery image from HP?  Does regular full system backup is good enough for recovery the whole system (Java + ABAP)? Thanks for your help.
    James

    You should back it up just like any other SAP system.  HP does not provide a new image if something happens.

  • I am extremely unsatisfied with the service, as a matter of fact I live outside United State (Venezuela) and the IPhone that I have received is not working, did not receive operator service for the MOVISTAR system which is the one I am affiliated with?

    The Iphone 4 which Dadeland store gave me cannot be used in Venezuela, I felt as I am being stolen from Apple

    DO you have a question for your fellow iphone users?
    Did you buy an unlocked iphone?  Does your receipt say unlocked?
    What happenswhen you try to activate your iphone with your SIM?
    Error message?
    What does it say?
    Any info about your isuue?

  • What is the effect of stopping the EFS service on a 2012 Domain Controller?

    Hello,
    The Encrypting File System service was started and is running on a production 2012 Domain Controller, which is not a standard in our shop.  What is the potential impact if I stop the service? 
    Thanks for your help! SdeDot

    Hi,
    Have you already encrypted files or folders using EFS service in your domain?
    If not, and you are not planning to use it to encrypt files or folders in the future, then it is OK to disable it.
    If you have encrypted files with EFS service, make sure that they are all decrypted before disabling the service, otherwise no users will be able to access them.
    More information for you:
    How to Disable or Enabled EFS Encryption in Vista, Windows 7, and Windows 8
    http://www.vistax64.com/tutorials/102501-encryption-disable-enable.html
    How to: Disable Encrypted File System (EFS) on Windows 2008 R2
    http://markswinkels.nl/2012/06/how-to-disable-encrypted-file-system-efs-on-windows-2008-r2/
    Please Note: Since these web sites are not hosted by Microsoft, these links may change without notice. Microsoft does not guarantee the accuracy of this information.
    Best Regards,
    Amy Wang

  • The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliant check cannot be completed, the server will automatically shut down in 0

    i need a help. I am new in company and have to solve this problem.
    My colleague did a migration from Small Business server 2003 to Foundation 2008, about 1 year ago. After few days, he got this error message in title. Server turn off about once a month. He worked following:
    joined new server Foundation to the Domain
    dcpromo on new Server
    migration (he said that he worked step-by-step with tutorial)
    demote on old Server SBS 2003
    disconnect old server from domain. This old is not in function now.
    New server have just 3 computer accounts. The Forest functional level is Server 2003.
    I've did dcdiag:
    C:\Users\Administrator>slmgr.vbs /dli
    C:\Users\Administrator>dcdiag
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = server2008
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\SERVER2008
          Starting test: Connectivity
             ......................... SERVER2008 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\SERVER2008
          Starting test: Advertising
             ......................... SERVER2008 passed test Advertising
          Starting test: FrsEvent
             ......................... SERVER2008 passed test FrsEvent
          Starting test: DFSREvent
             ......................... SERVER2008 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... SERVER2008 passed test SysVolCheck
          Starting test: KccEvent
             ......................... SERVER2008 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... SERVER2008 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... SERVER2008 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... SERVER2008 passed test NCSecDesc
          Starting test: NetLogons
             ......................... SERVER2008 passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... SERVER2008 passed test ObjectsReplicated
          Starting test: Replications
             ......................... SERVER2008 passed test Replications
          Starting test: RidManager
             ......................... SERVER2008 passed test RidManager
          Starting test: Services
             ......................... SERVER2008 passed test Services
          Starting test: SystemLog
             A warning event occurred.  EventID: 0x8000001D
                Time Generated: 03/08/2012   09:59:45
                Event String:
                The Key Distribution Center (KDC) cannot find a suitable certificate
     to use for smart card logons, or the KDC certificate could not be verified. Sma
    rt card logon may not function correctly if this problem is not resolved. To cor
    rect this problem, either verify the existing KDC certificate using certutil.exe
     or enroll for a new KDC certificate.
             An error event occurred.  EventID: 0xC0001B61
                Time Generated: 03/08/2012   10:09:56
                Event String:
                A timeout was reached (30000 milliseconds) while waiting for the Liv
    eUpdate service to connect.
             An error event occurred.  EventID: 0xC0001B58
                Time Generated: 03/08/2012   10:09:56
                Event String:
                The LiveUpdate service failed to start due to the following error:
             ......................... SERVER2008 failed test SystemLog
          Starting test: VerifyReferences
             ......................... SERVER2008 passed test VerifyReferences
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : BREG
          Starting test: CheckSDRefDom
             ......................... BREG passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... BREG passed test CrossRefValidation
       Running enterprise tests on : BREG.local
          Starting test: LocatorCheck
             ......................... BREG.local passed test LocatorCheck
          Starting test: Intersite
             ......................... BREG.local passed test Intersite
    C:\Users\Administrator>
    I did nslookup:
    C:\Users\Administrator>nslookup
    Default Server:  UnKnown
    Address:  ::1
    and this:
    C:\Users\Administrator>ntdsutil
    ntdsutil: roles
    fsmo maintenance: connections
    server connections: connect to server server2008
    Binding to server2008 ...
    Connected to server2008 using credentials of locally logged on user.
    server connections: q
    fsmo maintenance: select operation target
    select operation target: list roles for connected server
    Server "server2008" knows about 5 roles
    Schema - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=BREG,DC=local
    Naming Master - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-
    Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
    PDC - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN=Si
    tes,CN=Configuration,DC=BREG,DC=local
    RID - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN=Si
    tes,CN=Configuration,DC=BREG,DC=local
    Infrastructure - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site
    -Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
    select operation target:
    Did also slmgr.vbs /dli and got:
    name:Windows Server(R) ServerWinFoundation edition
    Description: Windows operating System - Windows Server(R),
    OEM_COA_NSLP channel
    Partial product key:.......
    License Status:Licensed
    thanks for help, in advance

    I forgot to say that it is the only DC in the domain.
    and this is DNS test
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       * Verifying that the local machine server2008, is a Directory Server.
       Home Server = server2008
       * Connecting to directory service on server server2008.
       * Identified AD Forest.
       Collecting AD specific global data
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=BREG,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=BREG,DC=local
       Getting ISTG and options for the site
       * Identifying all servers.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=BREG,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers
       Getting information for the server CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.
       * Found 1 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\SERVER2008
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             Determining IP4 connectivity
             * Active Directory RPC Services Check
             ......................... SERVER2008 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\SERVER2008
          Test omitted by user request: Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Test omitted by user request: FrsEvent
          Test omitted by user request: DFSREvent
          Test omitted by user request: SysVolCheck
          Test omitted by user request: KccEvent
          Test omitted by user request: KnowsOfRoleHolders
          Test omitted by user request: MachineAccount
          Test omitted by user request: NCSecDesc
          Test omitted by user request: NetLogons
          Test omitted by user request: ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Test omitted by user request: Replications
          Test omitted by user request: RidManager
          Test omitted by user request: Services
          Test omitted by user request: SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Test omitted by user request: VerifyReferences
          Test omitted by user request: VerifyReplicas
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
             See DNS test in enterprise tests section for results
             ......................... SERVER2008 passed test DNS
       Running partition tests on : ForestDnsZones
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : DomainDnsZones
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : Schema
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : Configuration
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : BREG
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running enterprise tests on : BREG.local
          Starting test: DNS
             Test results for domain controllers:
                DC: server2008.BREG.local
                Domain: BREG.local
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                   TEST: Basic (Basc)
                      The OS
                      Microsoft Windows Server 2008 R2 Foundation  (Service Pack level: 1.0)
                      is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter
                      [00000007] Intel(R) 82566DM-2 Gigabit Network Connection:
                         MAC address is 00:19:99:86:E9:62
                         IP Address is static
                         IP address: 192.168.1.250
                         DNS servers:
                            192.168.1.250 (server2008.breg.local.) [Valid]
                            127.0.0.1 (server2008.breg.local.) [Valid]
                      The A host record(s) for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders are not configured on this DNS server
                      Root hint Information:
                         Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
                         Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
                         Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
                         Name: d.root-servers.net. IP: 128.8.10.90 [Valid]
                         Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
                         Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
                         Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
                         Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unreachable)]
                         Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
                         Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
                         Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
                         Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
                         Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreachable)]
                         Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
                         Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
                         Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
                         Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
                         Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
                   TEST: Delegations (Del)
                      Delegation information for the zone: BREG.local.
                         Delegated domain name: _msdcs.BREG.local.
                            DNS server: server2008.breg.local. IP:192.168.1.250 [Valid]
                   TEST: Dynamic update (Dyn)
                      Warning: Failed to add the test record dcdiag-test-record in zone BREG.local
                      [Error details: 9017 (Type: Win32 - Description: DNS bad key.)]
                      Test record dcdiag-test-record deleted successfully in zone BREG.local
                   TEST: Records registration (RReg)
                      Network Adapter
                      [00000007] Intel(R) 82566DM-2 Gigabit Network Connection:
                         Matching CNAME record found at DNS server 192.168.1.250:
                         cb30439d-35e0-4add-ae6c-e7f281295520._msdcs.BREG.local
                         Matching A record found at DNS server 192.168.1.250:
                         server2008.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.221dc40b-9d51-48cf-a3a3-e3daf251197f.domains._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._udp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kpasswd._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.gc._msdcs.BREG.local
                         Matching A record found at DNS server 192.168.1.250:
                         gc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _gc._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.pdc._msdcs.BREG.local
                         Matching CNAME record found at DNS server 192.168.1.250:
                         cb30439d-35e0-4add-ae6c-e7f281295520._msdcs.BREG.local
                         Matching A record found at DNS server 192.168.1.250:
                         server2008.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.221dc40b-9d51-48cf-a3a3-e3daf251197f.domains._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._udp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kpasswd._tcp.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _kerberos._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.gc._msdcs.BREG.local
                         Matching A record found at DNS server 192.168.1.250:
                         gc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _gc._tcp.Default-First-Site-Name._sites.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.BREG.local
                         Matching  SRV record found at DNS server 192.168.1.250:
                         _ldap._tcp.pdc._msdcs.BREG.local
             Summary of test results for DNS servers used by the above domain
             controllers:
                DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:1::803f:235              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:2d::d (d.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2d::d              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:2f::f (f.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2f::f              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:3::42 (l.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:3::42              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:ba3e::2:30              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:c27::2:30              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:7fd::1 (k.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fd::1              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:7fe::53 (i.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fe::53              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:dc3::35 (m.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:dc3::35              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 128.63.2.53 (h.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 128.8.10.90 (d.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.112.36.4 (g.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.168.1.250 (server2008.breg.local.)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
                   DNS delegation for the domain  _msdcs.BREG.local. is operational on IP 192.168.1.250
                DNS server: 192.203.230.10 (e.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.228.79.201 (b.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.33.4.12 (c.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.36.148.17 (i.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.5.5.241 (f.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.58.128.30 (j.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 193.0.14.129 (k.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 198.41.0.4 (a.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 199.7.83.42 (l.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 202.12.27.33 (m.root-servers.net.)
                   All tests passed on this DNS server
             Summary of DNS test results:
    Auth Basc Forw Del  Dyn  RReg Ext
                Domain: BREG.local
                   server2008                   PASS PASS PASS PASS WARN PASS n/a  
             ......................... BREG.local passed test DNS
          Test omitted by user request: LocatorCheck
          Test omitted by user request: Intersite

  • Can I monitor the users who are logged in Domain Controller?

    Can I monitor which users are logged in the Domain Controller? Is there any features or hidden in Windows Server 2008 R2?
    it may be funny.but i just want to know.
    Thanks in Advance

    I am using a bat script assigned on the user Logon, this script will send you a notification each time user login 
    User Configuration --> Windows Settings --> Scripts (Logon/Logoff)
    download the exe from here and save it to shared folder(\\server\folder\)
    http://caspian.dotconf.net/menu/Software/SendEmail/
    (make sure to save it as a .bat)
    \\server\folder\sendEmail.exe -f [email protected] -t [email protected] -u User Logon -m User %USERNAME% has logged onto %COMPUTERNAME% on %DATE% at %TIME% -s smtpserver.mycompany.com:25

  • Maintain access to network(shared folders) resources if the site loses access to a Domain Controller?

    Scenario
    Windows 7 users log on to workstations at a site. Domain Controller is up and does the domain authentication for those users across the WAN. Users are then accessing a local(same building) Shared directory on a Windows 2008r2 server, in order to open, modify,
    save new files, etc.
    Then, the site loses access to the Domain Controller due to a WAN outage.
    Question
    Will those users that have already logged onto their Windows 7 workstations continue to have access to the shared resources on the local Windows 2008r2 server with their cached credentials(assuming they don't logoff or restart their machines)?? This has
    been the case in the past, but wondering if anything has changed with Windows 2008??
    Thanks

    Hi,
    The duration that you can access the server depends on when the server requires re-authentication.
    In Windows implementation, SMB session expiration is enforced based upon the client’s support of dynamic re-authentication capability [MS-SMB].
    If the client enables the CAP_DYNAMIC_REAUTH capability bit, the server will enforce session expiration. If a client does not set CAP_DYNAMIC_REAUTH, the Windows server does not return STATUS_NETWORK_SESSION_EXPIRED. 
    The SMB dynamic re-authentication feature was introduced in Windows XP. From there, Windows-based clients set the CAP_DYNAMIC_REAUTH capability bit to indicate to the server that the client supports re-authentication when the Kerberos service ticket for
    the session expires.
    Windows servers do check CAP_DYNAMIC_REAUTH:
    If clientCapabilities sets CAP_DYNAMIC_REAUTH, the server will set Server. Session.AuthenticationExpirationTime to the expiry time returned by AcceptSecuirtyContext.
    If clientCapabilities does not set CAP_DYNAMIC_REAUTH, the server will not set Server. Session.AuthenticationExpirationTime, basically a CAP_DYNAMIC_REAUTH capability bit not set by the client means the session will not expire on the server side.
    To configure Maximum lifetime for service ticket, you can use grouppolicy. The default value of
    Maximum lifetime for service ticket
    in Default Domain Policy is 600 minutes.
    Note:This setting is applied to DC, not clients.
    For detailed information, please view the link below
    CIFS and SMB Timeouts in Windows
    http://blogs.msdn.com/b/openspecification/archive/2013/03/19/cifs-and-smb-timeouts-in-windows.aspx
    Maximum lifetime for service ticket
    http://technet.microsoft.com/en-us/library/jj852188.aspx
    Hope this helps.
    Steven Lee
    TechNet Community Support

  • Error determining whether the target server is already a domain controller: The target server is already a Domain Controller.

    So basically, I was promoting a new server to a DC.  It said the promotion failed.  I rebooted the server and low and behold, it is acting like a domain controller.  It is moved to the domain controller OU, it is replicating fine, it knows
    who has the FSMO roles and I see no other problems. However, server manager is still telling me to promote the machine to be a DC as can be seen here:
    If I click the link to run DC Promo, I get this:
    Is there any way to just tell the server that "yes this is a working DC" to get rid of the task in server manager? Or is there something else I should do to correct this?

    Hi Vinny,
    There are others who have encountered similar scenarios as yours, clicking the Post-deployment Configuration message is enough to make the message disappear for good.
    Although I am more worried about that you mentioned the promotion failed, I suggest you run DCdiag.exe on this machine to examine if the DC is healthy.
    More information for you:
    Server 2012 DC Promotion Bug
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/221ed1ff-fc16-4c5d-ae05-edea7a9076be/server-2012-dc-promotion-bug?forum=winserverDS
    Troubleshooting Domain Controller Deployment
    http://technet.microsoft.com/en-us/library/jj592690.aspx
    Best Regards,
    Amy

  • After updating, Firefox informed me that Constant Guard, the security system which is provided by Comcast, is not compatible with this update and was disabled. WHY? Will Firefox now automatically provide security against online threats?

    Firefox upgraded automatically; in doing so, it stated that Constant Guard Security Suite, which is provided by Comcast, my internet service, is not compatible, and had to be disabled. Please explain why; is Firefox providing anti-virus when I surf the internet? If not, this is NOT an 'upgrade' and I will never use Firefox. Please respond as soon as possible.

    Hi, Thanks for that further bug description In Your Last Message That Describes The Problem I Am Having perfectly and is exactly the same for me.
    unfortunately that fix for my camera Powershot G6 does not work or apply as the view pictures switch is different on G6 is not usable during download as once you plug in DC/USB cable it turns off, and makes no diff and problem still exists exactly as you just described.
    thanks anyways "Selz Boy"
    it has been 17 days since apple promised to get back to me within 3-5 days hopefully with a solution, but I have still not heard from them.
    They blew me off, i guess, probably i will have to wait for new Yosemite OS update, which they pre-warned me could take as much as 6 months.
    I cannot believe apple released this new update with such major bug issues for camera downloads and that horrible "Photos" pgm which has all sorts of downgrades in features, usefulness and new bugs compared to iPhotos which I just finally got used to and was much better software.
    I am starting to lose faith in Apple and I am getting that Microsoft "FEEL" like I used to have when I was a PC user, which was why I originally switched to Apple  computers in first place.
    Oh well got my fingers crossed here.
    Thankfully the memory card reader solution  is working well, but cost me $45.

  • Refresh of DEV from PRD

    Hi, SAP Gurus!
    For our upgrade project, we need to refresh the DEV system from a recent copy of PRD. Our dev system must contain only configuration (i.e. no user data). This needs to be a new system with only ONE client in it. PRD and QAS are also single client systems.
    We have not been able to find any official SAP document on this procedure.Seems like a standard procedure, so there should be a documented guide out there.
    We are under a WIndows 2003 + Oracle 9i setup and running R3 Enterprise 4.7 ext. 2.00.
    DEV is the domain controller for STMS.
    Any ideas you can provide are wellcomed.
    MC

    Hi,
    For your scenario it seems you need to go with client copy , but
    This needs to be a new system with only ONE client in it
    But this doesnot means it is new system either you can create new client in DEV or can overwrite any existing client.
    For copying only configuration refer this link
    https://cw.sdn.sap.com/cw/docs/DOC-33675
    Other option is system copy but that will replicate your PRD data including master and transaction(I guess that is not required).
    So you need to explore client copy option for your requirement.
    Regards,

Maybe you are looking for

  • Aperture Library Browser - cant see photos from iPhone in Smart Library

    I have just upgraded my iLife 09 with iPhoto. I manage all my images from cameras in Aperture on the same Mac. I know the Aperture Browser is limited and is unable to show me the raw from my canon dslr however I notice that I cannot see the photos fr

  • PR created by MRP only one item each PR

    Hi Gurus, I ran MRP using T-Code MD01. Running succesful. But when I check PR created only had one material each PR, so too many PR Created in the system. The requirement is How can we run MRP then PR created in lot (each PR has many items) ? I've se

  • Feature Request: intuative live preview button

    Every singe ******* time. I click "Live Preview" only to see the message, "Open an HTML file in order to launch live preview," because I happen to have a CSS or JS file selected. I'd love to have the app be a little smarter and make an educated guess

  • Canon 6D issues with tethering....

    Hi All, Anyone know whats going on with being able to tether direct to LR 4.4 with a Canon 6D...its so frustrating when my camera keeps reading busy when I wish I was busy taking shots and not scratching my head trying to figure out what can be so di

  • Iphone 3G  GPS function

    Hi, Has anyone recently been having trouble with their Map App? The GPS function do not track me accurately... I could be 2 blocks away or 20 blocks away. It also does not smoothly track my position either, all over the map. Plus the range for the po