Windows Server 2012 R2 Connection Broker migration

Hi All,
I'm in the process of a VMware to Hyper-V migration and whilst in the process rather than migrating the 2012 RDS VM's over to Hyper-V I have decided to setup a bunch of 2012 R2 VMs. My original setup was
1 x Windows Server 2012 VM running RDSCB, RDSGW & RDSWA
2 x Windows Server 2012 VMs running RDSSH
My new environment runs
1 x Windows Server 2012 R2 VM running RDSCB, RDSGW & RDSWA
2 x Windows Server 2012 R2 running RDSSH
I have the connection broker running in HA mode for SSO purposes and publishing the correct name.  This also made life easier when running the upgrade as I joined the new 2012 R2 VM to connection broker group which worked fine. 
I then set the new 2012 R2 RDSCB VM as the active connection broker.  At this point the old 2012 VM was decommissioned (Without the RDS roles removed). As the old 2012 VM is now offline and un contactable when I add any new session hosts to the collection
I see an error stating it can't contact the old 2012 RDSCB.
I have been through the RDS connection broker database and removed any reference to the old RDSCB VM but this hasn't helped.  Does anybody have any other ideas or would you suggest re creating the collections from scratch?
Alex

Hi Alex,
To avoid future problems I recommend you wipe out the RDS deployment and recreate it again so that you will have a fresh database.  There is no need to switch to HA mode just so that you can change the published name.  I created a cmdlet that allows
you to change it in non-HA environments:
Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
-TP

Similar Messages

  • New Windows Server 2012 unable connect to Netlogon Service or update DNS records

    Hi everybody, all of my Windows Servers 2012 decided to collapse after innocuous group policy update that was meant to make user passwords more secure.
    The AD and DNS seem to be functioning "normally", I am able to add new Windows7 and Windows Server 2008 machines to the domain, I can see them in listed in the AD and DNS record are update correctly, however, as soon as I try to join Windows Server
    2012 it breaks.
    The event log is littered on the new server with:
    The system failed to register host (A or AAAA) resource records (RRs) for network adapter
    with settings:
               Adapter Name : {DB7F73CE-E011-4F3C-BEBC-2CE7A871DF51}
               Host Name : CHEETAH
               Primary Domain Suffix : somedomain.com
               DNS server list :
    192.168.0.5
               Sent update to server : <?>
               IP Address(es) :
    192.168.0.15
    The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running
    at this time.
    You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
    and
    Name resolution for the name _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.somedomain.com. timed out after none of the configured DNS servers responded.
    When I try to ping the primary DC (WS2003) it fails, the Secondary DC (WS2012) responds.
    The >nltest /sc_query:somedomain.com on Windows Servers 2012 returns:
    Flags: 0
    Trusted DC Name
    Trusted DC Connection Status Status = 1311 0x51f ERROR_NO_LOGON_SERVERS
    The command completed successfully
    yet it works on all other machines.
    I tried removing 2012 servers from the domain and rejoining - without success. The cookie crumbled when I added two new installations of Windows Server 2012 & 2008 and 2008 worked fine but 2012 showed same symptoms.
    There is one peculiar thing that I had noticed on all Windows 2012 machines, it constantly showing "Workplace Connection - Connecting" in the networks pane on the right side of the screen, which I can't say i ever noticed before.
    Unfortunately, the secondary DC is a multihoming server with Direct Access role - I am not sure if this may play some part but our existing configuration worked for a year now without any problems. Issue appeared when I changed the password complexity rule,
    which boggles the mind. I wonder if there has been some other changes in GPO that did not propagate from years ago and finally comeback to break things.
    Any suggestions would be really appreciated.
    wmin

    Hello Ace, i wish you a Happy New Year! I hope your break was enjoyable and filled with cheer.
    In the end I had to bite the bullet and reinstall all troublesome servers. Your recommendations from above removed some serious problems with the DA and DNS resolution.
    I was able to attach new server to the domain without any problems and begin painful process of rebuild.
    I have promoted TIGER to full DC controller role, but having some issues with replication. Although running >repadmid /showrepl gives positive
    feedback, the sysvol folder on the secondary DC is empty.
    Also there is a couple of warnings in the event log:
    Event ID 4012
    Log Name: DNS Server
    Source: DNS-Server-Service
    The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial
    synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server
    for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
    - which has not repeated since 3rd of Jan.
    These events occur on the primary DC every few minutes:
    Event ID 1030
    Source: Userenv
    Log Name: NT AUTHORITY\SYSTEM
    Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Event ID 1058
    Source: Userenv
    Log Name: NT AUTHORITY\SYSTEM
    Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=somedomain,DC=com. The file must be present at the location <\\somedomain.com\sysvol\somedomain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.
    (The network name cannot be found. ). Group Policy processing aborted.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Should sysvol folder be shared on the secondary DC? Another interesting thing to point out is that
    \\somedomain.com\sysvol\somedomain.com\Policies\ can be access
    from all other machines except the DC1.
    Cheers!
    kind regards,
    wmin

  • Windows Server 2012 Essentials Connection Software not working

    This comes in response to a ticket I got great help from a user on but I'm still stuck on the connection software bit.
    Original Thread: http://social.technet.microsoft.com/Forums/windowsserver/en-US/0a7e6d91-98c7-42f2-9cdd-66117df91d76/win-2012-essentials-not-allowing-client-connections?forum=winserveressentials#0a7e6d91-98c7-42f2-9cdd-66117df91d76
    Summary: All my machines 8 of them up to now have been adding machines using the servername/connect
    Well I have 2 new HP's here Win 7 Pro all updated that WILL NOT get past the asking for the server username/pass screen of the connects software install. I can get them onto the server manually and my GP applies fine, my roaming profiles are working, the
    computer is seen in AD but I have none of the features that are provided by the connect software like dashboard viewing and backups etc.
    The error I get is "The server is not available. Try connecting this computer again, or for more information, see Troubleshoot connecting computers to the server"
    Anyone have any ideas?

    Hi James,
    Based on your description, “Well I have 2 new HP's here Win 7 Pro all updated that WILL NOT get past the
    asking for the server username/pass screen of the connects software install.”, would you please let me confirm whether have reached the page of Windows Server Essentials Connector Configuration Wizard as below picture shows, then can’t go through?
    àI can get them
    onto the server manually and my GP applies fine, my roaming profiles are working, the computer is seen in AD
    Did you mean that add the client computer to windows essentials domain by using traditional method (change
    Workgroup to Domain in System Properties)?
    When this issue occurred, please ping server from the problematic client computer by using server name and
    IP address. Then monitor the result.
    Meanwhile, I noticed your
    original thread that Howtodo have provided some suggestions. As he mentioned, would you please check if Connector software had been installed? Please alos check ClientDeploy log file.
    By the way, did you add the client computer to windows server essentials network via wireless?
    Hope this helps.
    Best regards,
    Justin Gu

  • Web Access for Remote Desktop on Windows Server 2012

    Hello,
    i've a Windows Server 2012 without a domain. So i installed the remote desktop session host, the remote desktop license server and the remote desktop gateway as a server role only. All is working fine. Without a domain, no management tools for remote
    desktop are available. So i configure the remote desktop via the registry. I define (via registry) some remoteapps, too. All values are copied from a running Windows Server 2008 R2. So the remoteapps are runing.
    Now i want to use the new Microsoft Remote Desktop client for Android. To use a remoteapp i must define a remote resource. To define a remote resource i need a url to the web access for remote desktop. So i installed the web access. But if i login to the
    web access, i don't see any remoteapp. What's wrong? I've set the ShowInTSWA to 1. What must i do to access an existing remoteapp via web access?
    Martin

    Hi Martin,
    Server 2012 RD Web Access is designed to retrieve published RemoteApps and Desktops from a Server 2012 RD Connection Broker and/or a Server 2008 R2 RD Session Host server.  From your description it doesn't appear that you are using either of the above.
    I know it is a more complicated set up, but you should consider having a domain, creating a RDS deployment, etc., so that you can use the full featureset as it was intended.  You can do it all on a single server if needed.  For Server 2012
    there is a hotfix that needs to be applied to permit RD Connection Broker to work on the same server instance as active directory.
    -TP

  • Activate windows server 2012 R2 after evaluation expired

    I installed windows server 2012 R2 evaluation version on 4 servers. The evaluation expired and the servers are shutting down automatically now. When I try to put the license key, it is not accepting it. I could activate some other servers with same license
    key; but before the evaluation time expired. I used the same media to install these serves as well. Kindly let me know if there is a way or workaround to make these servers licensed.
    Regards.

    Hi,
    Did the problematic Windows Server 2012 R2 connect to Internet when attempt to activate the server? Please also
    refer to Converting evaluation versions of Windows Server 2012 to full retail versions section in following article and check if can help you.
    Evaluation Versions and Upgrade Options for
    Windows Server 2012
    à
    When I try to put the license key, it is not accepting it.
    By the way, did you get any error message when can’t activate the problematic server?
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu
    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]

  • Is Windows 2003 member servers still able to authenticate against Windows Server 2012 R2 AD after mirgation?

    Hi,
    We are planning to migrate Windows Server 2008 R2 AD to Windows Server 2012 R2 AD. But we have some Windows 2003 member servers (Running RADIUS for VPN user to authenticate their AD accounts). Does anyone know that existing Windows 2003 member
    servers still able to authenticate on Windows Server 2012 R2 AD after migration and function properly?  Just wanted to make sure Windows Server 2012 AD support Windows 2003 member server.
    Thanks.
    M

    Hi,
    Thanks for your post.
    Is there any Windows server 2003 domain controller in your domian?
    If yes, i think you could refer to this article:
    http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.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]

  • Is SQL Server 2008 R2 earliest version that can be used for RD Connection Broker in Windows Server 2012?

    I am setting up redundancy for another RD Connection Broker? What is the earliest version of SQL that i can use in Windows Server 2012?

    Hi,
    SQL Server 2008 R2 is listed as the minimum version.  I have not tried earlier versions for use with RDCB.
    RD Connection Broker High Availability in Windows Server 2012
    http://blogs.msdn.com/b/rds/archive/2012/06/27/rd-connection-broker-high-availability-in-windows-server-2012.aspx
    -TP

  • DirectAccess Client not connecting without error code on Windows Server 2012 R2 and Windows 8.1

    Hello,
    we are currently migrating from Windows Server 2012 to 2012 R2 and are not able to get the new Direct Access Service up and running. Our goal is to establish DirectAccess connection for a handful of clients using the IPHTTPS-adapter on the default port 443.
    Errors:
    There is actually no error showing up. It seems the infrastructure tunnel cannot be created but none of the IPv6-transition adapters is connecting (teredo and 6-to-4 are down) and the IPHTTPs adapter gives no informations about a problem:
    >Get-DAConnectionStatus
    Status    : Error
    Substatus : CouldNotContactDirectAccessServer
    >Get-NetIPHttpsState
    LastErrorCode   : 0x0
    InterfaceStatus : Failed to connect to the IPHTTPS server; waiting to reconnect
    Setup:
    Our setup is a virtualized Windows Server 2012 R2 Standard running on Hyper-V. It is located behind a NAT having the Port 443 mapped to the server. The only role installed after the basic install is RRAS including DirectAccess and VPN. The assistants completed
    successfully (running the configuration for DirectAccess and VPN). Operation Status says everything is green und working (for multiple days in the meanwhile). A previous direct access installation (on a different machine running Windows Server 2012) has
    been removed before installing the new server. The new installation is using a different router, so this might also be the cause of a problem.
    The client is a Windows 8.1 notebook located outside the company network accessing the internet through another NAT-device. The client has been able to connect to the previous DirectAccess setup but has never been able to establish a connection after the
    setup of the new Direct Access server. The device has no outbound constraints concerning the NAT-device and is only running the integrated Windows Firewall.
    Diagnosis:
    So far I've done some basic DNS and connectivity checks. The DNS-name can be resolved correctly and the router even responds to pings. The port forward is working and HTTPs connections are generally possible (temporarily routed the port to
    access the NLS-Website located on the server, which worked fine).
    Network monitor shows that both computers are communicating, traffic on the expected Port 443 is incoming on the server and responses from the server reach the client.
    Opening the IPHTTPs-url and in an endless page load. Sometime the browser page closes but I've never seen any result. Using telnet on the port shows that the server is accepting connections. I've even build a small test application that does a GET-Request
    on the URL returning HTTP-200 and no content.
    I'm currently running out of ideas what to do and since no error occurs this is kind of a bit frustrating. Any help appreciated.
    Regards
    Matthias

    Hi,
    In addition, have you disabled the DA client components on the DA client? If no, please also check
    the settings on the Name Resolution Policy Table.
    More information:
    DirectAccess
    Client Location Awareness – NRPT Name Resolution
    In addition, error 0x4C9 means the remote computer refused the network connection. It may be due to the invalid
    registry or corrupt drivers. For more detailed information, please refer to the link below:
    Error 1225 - Error Code 0x4C9
    Note:
    Microsoft is providing this information as a convenience to you. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best regards,
    Susie

  • Migration of Windows Small Business Server 2003 to Windows Server 2012 Essentials

    Hi,
    I am trying to migrate Windows Small Business Server 2003 to Windows Server 2012 Essentials by following the steps given in the link below:
    http://technet.microsoft.com/en-us/library/jj200112.aspx
    I have looked at other threads on the forum but none of them have been too helpful.
    The issue: When
    I run the Migration Preparation Tool on the Source Server, it runs successfully and does not report any errors. However, when I try installing Windows Server 2012 Essentials on the Destination Server, it displays an error that says 'Source
    Server not prepared for migration: After you run the Migration Preparation Tool successfully on your source Server, click retry'.
    The Source Server has 2 network adapters-one for the local network and the other for connection to the internet and the router is set as the default gateway this adapter.
    Since it is mentioned in the documentation - 'configure your Source Server to use one network adapter', I'm wondering if this is the issue and I need to make changes in this configuration? 
    On running the Microsoft IT Environment Health Scanner tool it
    reported an error - 'DNS Server listening on multiple addresses' and a warning ‘Domain Controller listening on multiple addresses’. Both point to the same solution KB 272294 (http://support.microsoft.com/kb/272294).
    But it did not remove the errors.
    Other steps performed:
    As per the steps, I performed a backup, installed recent service packs and synchronized the source server time with external source.
    On running the Best Practices Analyser. It shows 3 warnings.
    - The threshold for the Allocated Memory alert is set to the default value. However the server has more than 2 GB of RAM installed.
    - Microsoft Outlook Client not installed" Text="Microsoft Outlook Client is not installed in the ClientApps folder. You must run Windows SBS integrated setup.
    - The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000. The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000.
    I also ran the Ran netdiag.exe, dcdiag.exe commands
    and no failures were reported.
    The Event Viewer does not show any errors.
    Not sure to what extent these warnings would affect the migration. 
    Any help would be appreciated. Thanks!

    The SBS2003 needs to use one NIC only so you'll need to change that before starting. If it is the premium version and has ISA server installed, that will need to be removed first.  See:
    http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx
    -- Al

  • Windows Domain Controller on Windows Server 2012 R2: Hyper-V roaming profiles not loading due to slow connection

    I have racked my brain and done everything that I know to do for about two weeks now.  I am setting up a new system at our fire department and I am having the worst luck with getting the workstations to login to the domain controller with roaming
    profiles.  It keeps telling me that the roaming profile could not be loaded because of a slow connection.  These are workstations that are connected directly to the switch that the DC is connected to.  I have tried multiple connections regarding
    the layout (DC into the router, router into the switch).  The router is a Cisco RV220W.  I have two VLANS, one for public and one for private domain.  The Private VLAN has DHCP turned off since I am providing it through the DC.  I currently
    have a connection from the Private VLAN going to the unmanaged switch that the workstations and server are plugged into.
    The server is a Dell PowerEdge R420 that has 6 NIC ports (1 dual port and 1 quad port).  I have a virtual switch setup on Hyper-V for an external port (let's say Card 2 Port 3) that is assigned to the WS 2012R2 Domain Controller.  The DC can see
    the internet fine and the workstations can connect to the shared folders on the server.  I can retrieve files by just using the computer name or FQDN.  The DC is also running DNS and DHCP.  The DNS has the _msdcs setup from when I installed
    the active directory role.  I have attempted to assign static IP addresses to the workstations:
    IP:                     10.0.0.80
    Subnet:             255.255.255.0
    IPV4 Gateway:  10.0.0.1
    IPV4 DNS:        10.0.0.12
    I've attempted "append the specific DNS suffix", I've "registered the connection in DNS", I've used "use this connections suffix in DNS registration".
    The server is assigned:
    IP:                     10.0.0.12
    Subnet:             255.255.255.0
    IPV4 Gateway:  10.0.0.1
    IPV4 DNS:         10.0.0.12
    The DNS entries have forwarders that forward to my ISP DNS servers for lookup
    I've enabled and disabled DHCP, I've installed a new VM just to create another DC to make sure that I didn't goof up when I created it.
    I've lost my patience with this project and am sinking fast.  Can someone please offer some advice as to what I've done wrong?  I've created this exact scenario at work many times but, I've never done it with Windows Server 2012.  Is this
    possibly something to do with the Dell PowerEdge server (Generation 12) with the SR-IOV?  I am going to attempt to work on it some more tomorrow when I get over there.  I think there may be an issue with the SR-IOV not being enabled on the machine
    through the Dell Bios.  Would the SR-IOV really cause the workstations to report a slow connection?  When I login at the domain controller the roaming profiles and folder redirection work fine so, I know the GPO settings are correct.  I don't
    have "ignore slow connections" or any of those GPO's set.  I need to get it working the correct way so, I didn't want to fool the server when there is another underlying problem.  Any help that someone can offer, I am more than willing
    to listen.  If you need more information, please ask.
    Thanks,
    Jay

    So, I've managed to research this some more since Thursday and I've come to the conclusion that Hyper-V does a horrible job of supporting Qualcomm NIC cards. That's the only thing I can conclude as far as where the issue is originating. I've read many
    post and walkthroughs but nothing that has helped. The issue wasn't with any settings in the domain controller. The issue was that there really is a slow connection originating at the domain controller that is a VM and has network connectivity through the
    virtual switch from Hyper-V. So, next question is, how do I get the DC to have better connectivity through the NIC that Hyper-V won't give it? If hyper-v would allow passthrough, this would be so much simpler. VM-ware is looking really good at this point.
    Im disappointed in MS right now.

  • Windows server 2012 and windows xp remote desktop connection loss

    I am having this problem for a month now, and i am stumped with trying to find an answer . I have talked with several network admins in my area and with no luck i have not found a solution. I have a windows server 2012 placed with 5 pcs that are connected
    on a local network , those 5 pc's connect to the server via remote desktop. List of pc's:
    1x Windows 7
    4x Windows XP SP3
    All have the latests network drivers, all have the latest version of remote desktop installed. All have been scanned for viruses. All have antivirus software.
    Problem is the 4 XP machines lose connection on when connected via remote desktop. If one starts losing connection the other 3 start to lose the connection aswell. The windows 7 machine is not affected by this it works fine.
    What have I tried:
    Scanning for viruses.
    Disabling Firewall and antivirus software.
    Updating all drivers.
    Did many changes to group policy like keepalives etc.
    Turning off SMBv2 SMBv3.
    Turning off network adapter Offload settings.
    Changed some registry settings like keepalive, smb etc.
    Updating every pc and server with all windows updates.
    Changed the router and switch.
    Port forwarded needed ports like 3389.
    Updating remote desktop to 7.0.
    I might be forgetting some stuff i will add as i remember anything.
    So the thing is this. I use a Windows XP machine from my office I remotely connect to the server via the Internet and I DO NOT experience any connection loss. BUT the XP machines on the local network constantly experience connection loss via remote desktop.
    I pinged every Machine from the server via CMD command PING. So when they lose connection the Packets get time outs . Packets get dropped between 1-10 packets when a connection is lost. This packet drop does not occur when using the internet or anything else.
    ONLY when connected to the server via remote desktop. The packets get dropped at random intervals.
    Problem is I use an XP machine and I am not experiencing any loss of connection , while the XP machines on the local network experience it , but not the windows 7 machine.
    Router is ASUS RT-N53 , and switch is Dlink DES-1008D. Server is a Dell PowerEdge T110 II.
    Can someone please tell me what can i do to solve this problem?

    So today got some word from their office. They were using RDP from 8AM until 12PM all was working fine. Then got back after lunch about 1PM and got a few connection lost errors when they tried using RDP again. Its weird since they didn't have disconnects
    in the morning, and started having them after lunch.
    Also noticed, that two pc were not using RDP and were disconnected as shown in task manager. And they still got request timeouts.
    Maybe this is not a remote desktop issue?
    TASK MANAGER
    The 2 disconnected pc's ping screens:

  • Remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

    remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
    does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
    or what's the problem,
    Mahmoud Sabry IT System Engineer

    this issue maybe will be fix by latest version, we still waiting for it
    maybe your issue can be fix using this methods
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
    http://shawn.meunier.com/?p=1#comment-43

  • DirectAccess Windows Server 2012 R2 and Windows 8.1 - status connecting

    I've successfully deployed DirectAccess on Windows Server 2012 R2 in a 2 node NLB cluster. Everything in the console is green and I can see clients connecting.
    Windows 7 clients can connect and with the DirectAccess connectivity assistant installed show as connected and I can access resources.
    On a Windows 8.1 client I can access resource and run the troubleshooting tool which reports no errors, but if I look at connections it shows as connecting and the status never changes to connected. Clients work correctly when on the internal network.
    I've looked at available hotfixes, but not found anything for when the status is incorrectly shown.
    Any ideas before I raise a support call?
    James Saunders

    Hi,
    You current information hardly determine which part may occur error, I found the similar symptom on the following third party article, may can give you some help.
    The similar issue third party article:
    Windows 8 DirectAccess client keeps saying "Connecting"
    http://tfs.letsblog.it/post/2013/07/10/Windows-8-DirectAccess-client-keeps-saying-Connecting.aspx
    More information:
    The Network Connection Status Icon
    http://blogs.technet.com/b/networking/archive/2012/12/20/the-network-connection-status-icon.aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • The restor pocess did not succeed because your computer cannot connect to the server - Windows Server 2012 R2 Essentials Experience

    Hi all
    I've been running Windows Server 2012 R2 with the Essentials Experience in test for a Windows 8.1 client environment, on an HP ProLiant MicroServer N54L. Overall I've found the Essential Experience set-up over WHS2011 and WHSv1 okay; still looking to extract
    any real value over the former versions.
    This box has been up and running for a few months now, with client backups of a Win 8.1 box scheduled and running successfully every day. However when trying to conduct any file restores from the backups, to the client, I receive an error dialog once I go
    through motions from the Dashboard:
    On the 'Devices' tab, right-click the appropriate client and select 'Restore files or folders for the computer'
    'Restore Files of Folders' dialog pops up, asking me to 'Choose a backup' from the list of all the backups that have run
    Select any one in the list - have tried numerous backups; automatic, manual, etc. same result every time
    Brings up the dialog to 'Choose a volume', choose either C: or D: partitions of the same fixed drive - again, no difference which one I choose, the outcome is the same
    'Opening the volume' dialog starts, with progress bar, runs to about 4% complete the pops up the dialog 'The restore process did not succeed'. Full error in the dialog, "The restore process did not succeed because your computer cannot connect to the
    server. Make sure that the computer is connected to the networkm and then try again
    If my computer cannot connect to the server - how can I get that far? How can I open the dashboard, select a client, select from a list of backups, select a volume to restore, etc. What is going on here?

    Hi,
    Please check if a "host" entry for the server is added to the client. For more detailed information, please refer to the threads below:
    Unable to Restore files or folders from a Client Backup
    http://social.technet.microsoft.com/Forums/en-US/d1d001bd-20c5-4f09-861d-526c31567963/unable-to-restore-files-or-folders-from-a-client-backup
    Can't restore anything
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/98e269b5-2bd1-449e-a213-e386ae15266f/cant-restore-anything?forum=winserveressentials
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • 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?

Maybe you are looking for