SimonRousingBerg commented 7 years ago

Hi when using this for RDS deployment on windows 2016 it enters an state of a reboot loop after i states "The deployment was successful" in an "xRDSessionDeployment". Then i hangs in that state, and never continues to the Collection or CollectionConfiguration???

Any ideas?

VERBOSE: Performing the operation "Start-DscConfiguration: SendMetaConfigurationApply" on target "MSFT_DSCLocalConfigurationManager". VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendMetaConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'. VERBOSE: An LCM method call arrived from computer 2016DSC02 with user sid S-1-5-21-662093251-837600086-2983080374-500. VERBOSE: [2016DSC02]: LCM: [ Start Set ] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [MSFT_DSCMetaConfiguration] VERBOSE: [2016DSC02]: LCM: [ Start Set ] [MSFT_DSCMetaConfiguration] VERBOSE: [2016DSC02]: LCM: [ End Set ] [MSFT_DSCMetaConfiguration] in 0.0140 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [MSFT_DSCMetaConfiguration] VERBOSE: [2016DSC02]: LCM: [ End Set ] VERBOSE: [2016DSC02]: LCM: [ End Set ] in 0.0420 seconds. VERBOSE: Operation 'Invoke CimMethod' complete. VERBOSE: Set-DscLocalConfigurationManager finished in 0.274 seconds. VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = TestConfiguration,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'. VERBOSE: An LCM method call arrived from computer 2016DSC02 with user sid S-1-5-21-662093251-837600086-2983080374-500. VERBOSE: [2016DSC02]: LCM: [ Start Compare ] VERBOSE: [2016DSC02]: [DSCEngine] Importing the module C:\Windows\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DscResources\MSFT_RoleResource\MSFT_RoleResource.psm1 in force mode. VERBOSE: [2016DSC02]: [DSCEngine] Importing the module C:\Program Files\WindowsPowerShell\Modules\xRemoteDesktopSessionHost\1.4.0.0\DscResources\MSFT_xRDSessionDeployment\MSFT_xRDSessionDeployment.psm1 in force mode. VERBOSE: [2016DSC02]: [DSCEngine] Importing the module C:\Program Files\WindowsPowerShell\Modules\xRemoteDesktopSessionHost\1.4.0.0\DscResources\MSFT_xRDSessionCollection\MSFT_xRDSessionCollection.psm1 in force mode. VERBOSE: [2016DSC02]: [DSCEngine] Importing the module C:\Program Files\WindowsPowerShell\Modules\xRemoteDesktopSessionHost\1.4.0.0\DscResources\MSFT_xRDSessionCollectionConfiguration\MSFT_xRDSessionCollectionConfiguration.psm1 in force mode. VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]Remote-Desktop-Services] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]Remote-Desktop-Services] VERBOSE: [2016DSC02]: [[WindowsFeature]Remote-Desktop-Services] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]Remote-Desktop-Services] The operation 'Get-WindowsFeature' started: Remote-Desktop-Services VERBOSE: [2016DSC02]: [[WindowsFeature]Remote-Desktop-Services] The operation 'Get-WindowsFeature' succeeded: Remote-Desktop-Services VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]Remote-Desktop-Services] True in 0.2600 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]Remote-Desktop-Services] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RDS-RD-Server] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RDS-RD-Server] VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-RD-Server] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-RD-Server] The operation 'Get-WindowsFeature' started: RDS-RD-Server VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-RD-Server] The operation 'Get-WindowsFeature' succeeded: RDS-RD-Server VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RDS-RD-Server] True in 0.2030 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RDS-RD-Server] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RSAT-RDS-Tools] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RSAT-RDS-Tools] VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' started: RSAT-RDS-Tools VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' succeeded: RSAT-RDS-Tools VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' started: RSAT-RDS-Gateway VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' succeeded: RSAT-RDS-Gateway VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' started: RSAT-RDS-Licensing-Diagnosis-UI VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' succeeded: RSAT-RDS-Licensing-Diagnosis-UI VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' started: RDS-Licensing-UI VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' succeeded: RDS-Licensing-UI VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RSAT-RDS-Tools] True in 0.6660 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RSAT-RDS-Tools] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RDS-Connection-Broker] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RDS-Connection-Broker] VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Connection-Broker] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Connection-Broker] The operation 'Get-WindowsFeature' started: RDS-Connection-Broker VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Connection-Broker] The operation 'Get-WindowsFeature' succeeded: RDS-Connection-Broker VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RDS-Connection-Broker] True in 0.2040 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RDS-Connection-Broker] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RDS-Web-Access] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RDS-Web-Access] VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Web-Access] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Web-Access] The operation 'Get-WindowsFeature' started: RDS-Web-Access VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Web-Access] The operation 'Get-WindowsFeature' succeeded: RDS-Web-Access VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RDS-Web-Access] True in 0.2020 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RDS-Web-Access] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RDS-Licensing] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RDS-Licensing] VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Licensing] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Licensing] The operation 'Get-WindowsFeature' started: RDS-Licensing VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Licensing] The operation 'Get-WindowsFeature' succeeded: RDS-Licensing VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RDS-Licensing] True in 0.2060 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RDS-Licensing] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Importing the module MSFT_xRDSessionDeployment in force mode. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Importing the module MSFT_xRDSessionDeployment in force mode. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Checking RDSH role is deployed on this node. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Getting list of RD Server roles. VERBOSE: [2016DSC02]: LCM: [ End Test ] [[xRDSessionDeployment]Deployment] False in 1.2290 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[xRDSessionCollection]Collection] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[xRDSessionCollection]Collection] VERBOSE: [2016DSC02]: [[xRDSessionCollection]Collection] Importing the module MSFT_xRDSessionCollection in force mode. VERBOSE: [2016DSC02]: [[xRDSessionCollection]Collection] Importing the module MSFT_xRDSessionCollection in force mode. VERBOSE: [2016DSC02]: [[xRDSessionCollection]Collection] Checking for existance of RDSH collection. VERBOSE: [2016DSC02]: [[xRDSessionCollection]Collection] Getting information about RDSH collection. VERBOSE: [2016DSC02]: LCM: [ End Test ] [[xRDSessionCollection]Collection] False in 0.7110 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[xRDSessionCollection]Collection] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[xRDSessionCollectionConfiguration]CollectionConfiguration] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[xRDSessionCollectionConfiguration]CollectionConfiguration] VERBOSE: [2016DSC02]: [[xRDSessionCollectionConfiguration]CollectionConfiguration] Importing the module MSFT_xRDSessionCollectionConfiguration in force mode. VERBOSE: [2016DSC02]: [[xRDSessionCollectionConfiguration]CollectionConfiguration] Importing the module MSFT_xRDSessionCollectionConfiguration in force mode. VERBOSE: [2016DSC02]: [[xRDSessionCollectionConfiguration]CollectionConfiguration] Testing DSC collection properties VERBOSE: [2016DSC02]: [[xRDSessionCollectionConfiguration]CollectionConfiguration] Getting currently configured RDSH Collection properties VERBOSE: [2016DSC02]: LCM: [ End Test ] [[xRDSessionCollectionConfiguration]CollectionConfiguration] False in 2.9200 seconds. VERBOSE: [2016DSC02]: LCM: [ FAILEDCompare ] Completed processing compare operation. The operation returned False. VERBOSE: Operation 'Invoke CimMethod' complete. VERBOSE: Time taken for configuration job to complete is 7.443 seconds VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'. VERBOSE: An LCM method call arrived from computer DESKTOP-DOOA2AM with user sid S-1-5-21-662093251-837600086-2983080374-500. VERBOSE: [2016DSC02]: LCM: [ Start Set ] VERBOSE: [2016DSC02]: [DSCEngine] Importing the module C:\Windows\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DscResources\MSFT_RoleResource\MSFT_RoleResource.psm1 in force mode. VERBOSE: [2016DSC02]: [DSCEngine] Importing the module C:\Program Files\WindowsPowerShell\Modules\xRemoteDesktopSessionHost\1.4.0.0\DscResources\MSFT_xRDSessionDeployment\MSFT_xRDSessionDeployment.psm1 in force mode. VERBOSE: [2016DSC02]: [DSCEngine] Importing the module C:\Program Files\WindowsPowerShell\Modules\xRemoteDesktopSessionHost\1.4.0.0\DscResources\MSFT_xRDSessionCollection\MSFT_xRDSessionCollection.psm1 in force mode. VERBOSE: [2016DSC02]: [DSCEngine] Importing the module C:\Program Files\WindowsPowerShell\Modules\xRemoteDesktopSessionHost\1.4.0.0\DscResources\MSFT_xRDSessionCollectionConfiguration\MSFT_xRDSessionCollectionConfiguration.psm1 in force mode. VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]Remote-Desktop-Services] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]Remote-Desktop-Services] VERBOSE: [2016DSC02]: [[WindowsFeature]Remote-Desktop-Services] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]Remote-Desktop-Services] The operation 'Get-WindowsFeature' started: Remote-Desktop-Services VERBOSE: [2016DSC02]: [[WindowsFeature]Remote-Desktop-Services] The operation 'Get-WindowsFeature' succeeded: Remote-Desktop-Services VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]Remote-Desktop-Services] in 0.2080 seconds. VERBOSE: [2016DSC02]: LCM: [ Skip Set ] [[WindowsFeature]Remote-Desktop-Services] VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]Remote-Desktop-Services] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RDS-RD-Server] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RDS-RD-Server] VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-RD-Server] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-RD-Server] The operation 'Get-WindowsFeature' started: RDS-RD-Server VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-RD-Server] The operation 'Get-WindowsFeature' succeeded: RDS-RD-Server VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RDS-RD-Server] in 0.2100 seconds. VERBOSE: [2016DSC02]: LCM: [ Skip Set ] [[WindowsFeature]RDS-RD-Server] VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RDS-RD-Server] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RSAT-RDS-Tools] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RSAT-RDS-Tools] VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' started: RSAT-RDS-Tools VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' succeeded: RSAT-RDS-Tools VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' started: RSAT-RDS-Gateway VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' succeeded: RSAT-RDS-Gateway VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' started: RSAT-RDS-Licensing-Diagnosis-UI VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' succeeded: RSAT-RDS-Licensing-Diagnosis-UI VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' started: RDS-Licensing-UI VERBOSE: [2016DSC02]: [[WindowsFeature]RSAT-RDS-Tools] The operation 'Get-WindowsFeature' succeeded: RDS-Licensing-UI VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RSAT-RDS-Tools] in 0.6780 seconds. VERBOSE: [2016DSC02]: LCM: [ Skip Set ] [[WindowsFeature]RSAT-RDS-Tools] VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RSAT-RDS-Tools] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RDS-Connection-Broker] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RDS-Connection-Broker] VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Connection-Broker] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Connection-Broker] The operation 'Get-WindowsFeature' started: RDS-Connection-Broker VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Connection-Broker] The operation 'Get-WindowsFeature' succeeded: RDS-Connection-Broker VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RDS-Connection-Broker] in 0.2030 seconds. VERBOSE: [2016DSC02]: LCM: [ Skip Set ] [[WindowsFeature]RDS-Connection-Broker] VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RDS-Connection-Broker] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RDS-Web-Access] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RDS-Web-Access] VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Web-Access] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Web-Access] The operation 'Get-WindowsFeature' started: RDS-Web-Access VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Web-Access] The operation 'Get-WindowsFeature' succeeded: RDS-Web-Access VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RDS-Web-Access] in 0.2060 seconds. VERBOSE: [2016DSC02]: LCM: [ Skip Set ] [[WindowsFeature]RDS-Web-Access] VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RDS-Web-Access] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[WindowsFeature]RDS-Licensing] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[WindowsFeature]RDS-Licensing] VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Licensing] Importing the module MSFT_RoleResource in force mode. VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Licensing] The operation 'Get-WindowsFeature' started: RDS-Licensing VERBOSE: [2016DSC02]: [[WindowsFeature]RDS-Licensing] The operation 'Get-WindowsFeature' succeeded: RDS-Licensing VERBOSE: [2016DSC02]: LCM: [ End Test ] [[WindowsFeature]RDS-Licensing] in 0.2060 seconds. VERBOSE: [2016DSC02]: LCM: [ Skip Set ] [[WindowsFeature]RDS-Licensing] VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[WindowsFeature]RDS-Licensing] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Importing the module MSFT_xRDSessionDeployment in force mode. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Importing the module MSFT_xRDSessionDeployment in force mode. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Checking RDSH role is deployed on this node. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Getting list of RD Server roles. VERBOSE: [2016DSC02]: LCM: [ End Test ] [[xRDSessionDeployment]Deployment] in 1.1990 seconds. VERBOSE: [2016DSC02]: LCM: [ Start Set ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Importing the module MSFT_xRDSessionDeployment in force mode. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Importing the module MSFT_xRDSessionDeployment in force mode. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Initiating new RDSH deployment. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] The deployment was successful. VERBOSE: [2016DSC02]: LCM: [ End Set ] [[xRDSessionDeployment]Deployment] in 44.9160 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: [] A reboot is scheduled to progress further. Configuration will be continued after the reboot. WARNING: [2016DSC02]: [] A reboot is scheduled to progress further. Configuration will be continued after the reboot. VERBOSE: [2016DSC02]: LCM: [ End Set ] VERBOSE: [2016DSC02]: LCM: [ End Set ] in 48.4900 seconds. VERBOSE: Operation 'Invoke CimMethod' complete. VERBOSE: Time taken for configuration job to complete is 48.816 seconds

bgelens commented 7 years ago

@SimonRousingBerg Could you share your configuration script so we can analyze this a bit better.

The message given by xRDSessionDeployment is that the computer has a pending reboot. It could be something external to your configuration. I would suggest inspecting the registry keys on this node that deal with pending reboot logic.

HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired
HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

Especially the last one can have lingering stuff in my experience and could need some manual cleaning.

You could also introduce the xPendingReboot resource in your configuration and have the xRDSessionDeployment take a dependency on it.

SimonRousingBerg commented 7 years ago

Hi bgelens

Sure.

It keeps rebooting before reaching the xRDSessionCollection Collection If i stop my powershell script and then start it again, then when it runs my configuration again its completing without any reboot... ???

region Remote Desktop Session Host Config

    #region Remote Desktop Session Host ConfigData
        $ConfigData_RemoteDesktopSessionHost = @{
            AllNodes = @(
                    @{
                        NodeName = $RemoteServerIPAddress
                        ComputerNameFQDN = "$($RemoteServerName).$($DomainFQDN)"
                        ConnectionBrokerFQDN = $RDConnectionBrokerFQDN
                        WebAccessServerFQDN = $RDWebAccessServerFQDN
                        CollectionName = $RDCollectionName
                        Credential = $DomainAdminCredentials
                        PSDscAllowPlainTextPassword = $true
                        PSDscAllowDomainUser = $true
                    }
                )
        }
    #endregion

    Configuration RemoteDesktopSessionHost
    {
        Import-DscResource -ModuleName PSDesiredStateConfiguration, xRemoteDesktopSessionHost

        Node $AllNodes.NodeName
        {
            LocalConfigurationManager {
                RebootNodeIfNeeded = $true                    
            }

            WindowsFeature Remote-Desktop-Services
            {
                Ensure = "Present"
                Name = "Remote-Desktop-Services"
            }

            WindowsFeature RDS-RD-Server
            {
                Ensure = "Present"
                Name = "RDS-RD-Server"
            }

            WindowsFeature RSAT-RDS-Tools
            {
                Ensure = "Present"
                Name = "RSAT-RDS-Tools"
                IncludeAllSubFeature = $true
            }

            If($Node.ComputerNameFQDN -ieq $Node.ConnectionBrokerFQDN)
            {
                WindowsFeature RDS-Connection-Broker
                {
                    Ensure = "Present"
                    Name = "RDS-Connection-Broker"
                }
            }

            If($Node.ComputerNameFQDN -ieq $Node.WebAccessServerFQDN)
            {
                WindowsFeature RDS-Web-Access
                {
                    Ensure = "Present"
                    Name = "RDS-Web-Access"
                }
            }

            If($Node.ComputerNameFQDN -ieq $Node.ConnectionBrokerFQDN)
            {
                WindowsFeature RDS-Licensing
                {
                    Ensure = "Present"
                    Name = "RDS-Licensing"
                }
            }

            xRDSessionDeployment Deployment
            {
                SessionHost = $Node.ComputerNameFQDN
                ConnectionBroker = $Node.ConnectionBrokerFQDN
                WebAccessServer = $Node.WebAccessServerFQDN
                PsDscRunAsCredential = $Node.Credential
                DependsOn = "[WindowsFeature]Remote-Desktop-Services", "[WindowsFeature]RDS-RD-Server"
            }

            xRDSessionCollection Collection
            {
                CollectionName = $Node.CollectionName
                CollectionDescription = "RDS Collection deployed $((Get-Date).ToString())"
                SessionHost = $Node.ComputerNameFQDN
                ConnectionBroker = $Node.ConnectionBrokerFQDN
                PsDscRunAsCredential = $Node.Credential
                DependsOn = "[xRDSessionDeployment]Deployment"
            }
            xRDSessionCollectionConfiguration CollectionConfiguration
            {
                CollectionName = $Node.CollectionName
                ConnectionBroker = $Node.ConnectionBrokerFQDN               
                TemporaryFoldersDeletedOnExit = $true
                SecurityLayer = "SSL"
                PsDscRunAsCredential = $Node.Credential
                DependsOn = "[xRDSessionCollection]Collection"
            }
        }
    }

    RemoteDesktopSessionHost -ConfigurationData $ConfigData_RemoteDesktopSessionHost -OutputPath $MOF_Step4_InstallRemoteDesktopServices
    Set-DscLocalConfigurationManager -Path $MOF_Step4_InstallRemoteDesktopServices -CimSession $CIMSession -Force -Verbose

    While((Test-DscConfiguration -Path $MOF_Step4_InstallRemoteDesktopServices -CimSession $CIMSession -Verbose -ErrorAction SilentlyContinue).InDesiredState -ne $true)        
    {
        Start-DscConfiguration -ComputerName $RemoteServerIPAddress -Path $MOF_Step4_InstallRemoteDesktopServices -Credential $RemoteServerCreds -Force -Verbose -Wait
        Start-Sleep -Seconds 30

        Get-DscConfigurationStatus -CimSession $CIMSession -Verbose
        Start-Sleep -Seconds 5
    }

    Get-DscConfigurationStatus -CimSession $CIMSession -Verbose -ErrorAction SilentlyContinue
#endregion

VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Checking RDSH role is deployed on this node. VERBOSE: [2016DSC02]: [[xRDSessionDeployment]Deployment] Getting list of RD Server roles. VERBOSE: [2016DSC02]: LCM: [ End Test ] [[xRDSessionDeployment]Deployment] True in 1.8140 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[xRDSessionDeployment]Deployment] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[xRDSessionCollection]Collection] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[xRDSessionCollection]Collection] VERBOSE: [2016DSC02]: [[xRDSessionCollection]Collection] Checking for existance of RDSH collection. VERBOSE: [2016DSC02]: [[xRDSessionCollection]Collection] Getting information about RDSH collection. VERBOSE: [2016DSC02]: LCM: [ End Test ] [[xRDSessionCollection]Collection] True in 0.9660 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[xRDSessionCollection]Collection] VERBOSE: [2016DSC02]: LCM: [ Start Resource ] [[xRDSessionCollectionConfiguration]CollectionConfiguration] VERBOSE: [2016DSC02]: LCM: [ Start Test ] [[xRDSessionCollectionConfiguration]CollectionConfiguration] VERBOSE: [2016DSC02]: [[xRDSessionCollectionConfiguration]CollectionConfiguration] Testing DSC collection properties VERBOSE: [2016DSC02]: [[xRDSessionCollectionConfiguration]CollectionConfiguration] Getting currently configured RDSH Collection properties VERBOSE: [2016DSC02]: LCM: [ End Test ] [[xRDSessionCollectionConfiguration]CollectionConfiguration] True in 6.4750 seconds. VERBOSE: [2016DSC02]: LCM: [ End Resource ] [[xRDSessionCollectionConfiguration]CollectionConfiguration] VERBOSE: [2016DSC02]: LCM: [ End Compare ] Completed processing compare operation. The operation returned True. VERBOSE: [2016DSC02]: LCM: [ End Compare ] in 11.2380 seconds. VERBOSE: Operation 'Invoke CimMethod' complete. VERBOSE: Time taken for configuration job to complete is 11.474 seconds VERBOSE: 192.168.0.171: An LCM method call arrived from computer 2016DSC02 with user sid S-1-5-21-662093251-837600086-2983080374-500.

DurationInSeconds : 14 Error : HostName : 2016DSC02 IPV4Addresses : {192.168.0.171, 127.0.0.1} IPV6Addresses : {fe80::9cc1:7165:bc68:8abb%6, ::2000:0:0:0, ::1, ::2000:0:0:0} JobID : {2A77E825-5532-11E7-AB4E-005056893AF8} LCMVersion : 2.0 Locale : da-DK MACAddresses : {00-50-56-89-3A-F8, 00-00-00-00-00-00-00-E0} MetaConfiguration : MSFT_DSCMetaConfiguration MetaData : Author: Simon; Name: RemoteDesktopSessionHost; Version: 2.0.0; GenerationDate: 06/19/2017 22:59:07; GenerationHost: DESKTOP-DOOA2AM; Mode : PUSH NumberOfResources : 9 RebootRequested : False ResourcesInDesiredState : {[WindowsFeature]Remote-Desktop-Services, [WindowsFeature]RDS-RD-Server, [WindowsFeature]RSAT-RDS-Tools, [WindowsFeature]RDS-Connection-Broker...} ResourcesNotInDesiredState : StartDate : 19-06-2017 22:59:21 Status : Success Type : Initial PSComputerName : 192.168.0.171

VERBOSE: 192.168.0.171: [2016DSC02]: LCM: [ End GetStatus] in 0.0180 seconds.

SimonRousingBerg commented 7 years ago

When using Get-DscLocalConfigurationManager it keeps saying it has an PendingConfiguration

bgelens commented 7 years ago

Sorry I didn't respond earlier.. Very busy with normal day job :)

If it is still PendingConfiguration, it means that the desired state was never achieved.

Just to exclude a couple of things, could you try preparing all nodes by installing roles and features separately , run windows update until fully patched, have all of them rebooted as many times as needed and than try to send the config to the nodes.

From my experience with this module is that you're chasing your own tail more than you want to. Especially if nodes are capable of internet connectivity. See my video on these resources from PSConfEU where I'm battling this behavior by accident.

Let me know if this gets you anywhere!

SimonRousingBerg commented 7 years ago

Hi I know the feeling :)

I made it work in an simple use case. I specified the same server as Session Host, Web Access Server and Connection Broker.

Then i researched the use of the New-RDSessionDeployment cmdlet, wich i can see is used in the Set-TargetResource in the "Deployment" resource. Because what i did not post in this thread, is that in my initial Configuration i specified other servers for the specific roles like this. By the way the configuration was applied to Server1.

$ConfigData_RemoteDesktopSessionHost = @{ AllNodes = @( @{ NodeName = $RemoteServerIPAddress ComputerNameFQDN = Server2 ConnectionBrokerFQDN = Server1 CollectionName = Server1 Credential = $DomainAdminCredentials PSDscAllowPlainTextPassword = $true PSDscAllowDomainUser = $true } ) }

But research tells me that, when running the New-RDSessionDeployment cmdlet, you must run it on the server you specify as the Connection Broker !

So I made some changes and know I am applying the configuration to Server1. BUT, think i found a bug in this DSC resource, because when applying it know, i fails during the [[xRDSessionCollectionConfiguration]CollectionConfiguration] Testing DSC collection properties

I believe the bug is in line 39, 101 and 140 caused by this code. $collectionName = Get-RDSessionCollection | % {Get-RDSessionHost $_.CollectionName} | ? {$_.SessionHost -ieq $localhost} | % {$_.CollectionName} The $localhost contains the name of Server1 which in this case only has the Connection Broker and Web Access Server roles installed.

In the xRDSessionCollection there is only this line of code when getting the RDSessionCollection data. $Collection = Get-RDSessionCollection -ErrorAction SilentlyContinue

Does this make any sense to who ever made this DSC Resource?

/Best regards Simon

SimonRousingBerg commented 7 years ago

I've just made the change in the resource and then its working :)

Is this on purpose or do I might have misinterpreted the use of this DSC Resource?

Replaced this: $collectionName = Get-RDSessionCollection | % {Get-RDSessionHost $_.CollectionName} | ? {$_.SessionHost -ieq $localhost} | % {$_.CollectionName}

With this: $CollectionName = Get-RDSessionCollection | % {Get-RDSessionHost $_.CollectionName} | % {$_.CollectionName}

In the file "C:\Program Files\WindowsPowerShell\Modules\xRemoteDesktopSessionHost\1.4.0.0\DSCResources\MSFT_xRDSessionCollectionConfiguration\MSFT_xRDSessionCollectionConfiguration.psm1" In line 39, 101 and 140

/Best regards Simon

bgelens commented 7 years ago

The resource assumes it is running on the Connectionbroker and that the Connectionbroker is also a Sessionhost. Not sure why this where is in place. This is IMO a flaw in the design. Great you got it working! I will put my attention on this Repo some more in a little while (working through a lot of backlog on a couple of other modules with more open PRs / issues first)

jootuom commented 7 years ago

+1 on this.

On a fresh install from original 2016 RTM media and after applying 09/2017 cumulative updates, this resource doesn't seem to be working properly at all.

I tried doing a deployment with this resource with everything being installed on the same server and running the configuration locally. It fails to set up the connection broker role properly and the server ends up in a reboot loop and never finishes configuration.

If you can get PowerShell open between reboots and Stop-DscConfiguration, you can clearly see it's stuck on the collection configuration.

danielboth commented 6 years ago

Looking at this issue, I think this was fixed here:

https://github.com/PowerShell/xRemoteDesktopSessionHost/commit/316e32f923592e523c918a209b9e85f23eea67bf#diff-2b5b10bd6b3aeef410e8864fd2569cc9R184

When modifying the code I had the same issue as @SimonRousingBerg, so fixed it by just doing a lookup of the collection, the whole logic before did not make any sense to me.

@johlju, I think it's ok to close this one.

johlju commented 6 years ago

Closing this as per previous comment. If this was closed in error then please reopen or comment on this issue.

dsccommunity / xRemoteDesktopSessionHost

Keeps rebooting in a loop #21

region Remote Desktop Session Host Config