I am working on some deployment scripts that will automatically add a Session Host to a new or existing collection at deployment. I am experiencing some inconsistency when it comes to the PowerShell CMDLETS for RDS. 

For instance: The CMDLET Get-RDSessionCollection works on some servers and not on other servers...using the same command syntax. 

The command I am trying to use as an example is: Get-RDSessionCollection -CollectionName "CollectionName" -ConnectionBroker "HA FQDN DNS name" I can never get any of the RDS CMDLETS to work when I use the HA FQDN name of the connection brokers. If I use the server FQDN of the active connection broker...it works most of the time (have notice it not working on a few servers). 

When trying to troubleshoot why the HA name doesn't work, when doing a packet capture...I don't even see DNS queries go out to try resolve the HA FQDN name I put in...I see DNS queries go out for the server FQDN though. 

Has anyone else experienced any issues with the CMDLETS? I am running Powershell as Administrator as well. 

Hi,

Is the windows feature "Desktop Experience" a requirement for enabling RemoteFX on a 2012R2 RD session host?

Regards,

Andreas

Hi everyone,

this is my first post ever on this Forum, so forgive me if I'm missing any basic term of use, but I'm in a bit of a trouble...

I read a lot about my problem, but I can't find any clear solution, so I'm writing here. This is my situation:

Win2012 R2 Server, Workgroup, only File Services and RDS Services installed. 5 RDS CAL installed "per user". RDS Licensing Server and CAL mode configured via "gpedit.msc" (I know, no Active Directory = trouble and no GUIs)

Then, into RD Licensing Manager window  I have 0 of 5 available, and I'm pretty sure that everything will stop working at the end of the 120 days grace period, since I already "renewed" my grace period by deletingHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

Is there any way to "uninstall" those 5 licenses, or to make my server "forget" them? Will a Domain Controller be a solution, since I read that Workgroup servers can't manage "per user" CALs?

Again, sorry for any lack of netiquette, I'm pretty new to this world.

Thanks a lot

Stefano

Hello

I'm having big problems since today with external links to RemoteApps.

I have configured one server with the functions ofRDGateway, RDLicensing,rdweb and 2 servers with the Session Host functions.

I have a certificate from GoDaddy running smoothly.

There are several PC's that canaccess the RemoteApps smoothly.

Since December 2014 the servers have been workingnormally and without major problems.

Introduction and Question

An application uses the Windows API call “enumprinters” to collect all shared printers within a user session on a terminal server. Sometimes some, or all, of the printers are missing in enumprinters, although they are visible in the devices and printers dialogue. This is what we call incorrect printer mapping.

To simplify this issue, the application was replaced by ShowPrinters.vbs, which can be found in the appendix.

Is there a possibility to ensure, that enumprinters always returns the correct and complete list of printers?

Setup of the machines

To recreate this issue, a minimum of three machines is proposed: A domain controller “DC”, a terminal server “TS” and a client “CLI”. All machines are virtual machines with access to 2 virtual processors, 2 GB RAM and a 20 GB hard drive.

To exclude any possible issues with the network connection, all machines should be connected to the same network. When using virtual machines, a host-only network can be used. All machines are configured to use the preferred DNS server at the DC.

Some printers, which are shared via network, are needed. To keep this setup simple, five printers are installed on the client.

Domain Controller “DC”

Windows 2012 R2 Standard Build 9600

• Step 1
  • Install a Windows Server 2012 R2 Standard and install all mandatory updates
• Step 2
  • Use “Server Manager” -> “Add Roles and Features” -> Installation Type “Role-based” -> choose the target “DC” -> Choose “AD DS” and “DNS”, each with standard settings -> install
  • Promote to domain controller -> “Add a new forest” with root domain name “domain.com” and standard configuration
  • Restart according to the installation process to finish the configuration for the domain
• Step 3
  • Add a new user “testuser” and make the user member of “Domain Users” and “Remote Desktop Users”
• Step 4
  • No actions required in this step

Terminal Server “TS”

Windows 2012 R2 Standard Build 9600

• Step 1
  • Install a Windows Server 2012 R2 Standard and install all mandatory updates
• Step 2
  • Add TS to the domain and restart
• Step 3
  • Use “Server Manager” -> “Add Roles and Features” -> Installation Type “Remote Desktop Services” -> “Quick Start” -> “Session-based” -> choose the target “TS” -> standard settings
  • Restart according to the installation process
• Step 4
  • Navigate to “\CLI” to see the five shared printers and open each one to allow the driver to be installed

Client “CLI”

Windows 8.1 Enterprise Build 9600

• Step 1
  • Install a Windows 8.1 Enterprise and install all mandatory updates
• Step 2
  • Add CLI to the domain and restart
• Step 3
  • Check, if “Remote Desktop Connection” to “ts.domain.com” with the “testuser” is operational.
• Step 4
  • Add five test printers using the “Add a printer” dialogue: “The printer… isn’t listed” -> “Add a local printer” -> “Create a new port”, “Local Port” -> Port Name “c:\temp\1” through “c:\temp\5” -> print driver “Generic”, “Generic / Text Only” -> printer names “1” through “5” -> sharing activated with standard settings.In the local test environment other printer drivers likeHP universal driverare used with the same result.
    

I currently use a Mac Mini with OS Yosemite 10.10.2 to remote into my Windows 7 computer at work. Is it possible to use both of my monitors when in a remote session? My version of Microsoft Remote Desktop is 8.0.15.

Thank you!

Hello, I have set up my server 2012 standard server and set it up as a DC and RRAS server, the VPN works perfectly but only one user can use it, the second user will always get error 800. there are enough IP slots in the LAN and it is correctly assigning a new IP address to each new user that connects, but only one can connect at a time without error - I have searched around and couldnt find anything conclusive - is this a licensing or configuration issue?

Thank you very much for your time and consideration,

Larry

Hello Frenz,

              I need your guidance to setup a RDS farm for session and VM collection. I have 03 VM's for session based and 02 physical &01 VM for VM based collection.

             Kindly help me to segregate the roles across 03 servers factoring HA.

Windows 2008 R2 gateway and rdweb on same server (RD)

Windows 2008 R2 session server (TS)

After some time the website rdweb with the published programs (RemoteApp Programs) is empty for the users. I have tried everything and it allways fix itself with a restart. But i know see that when this problem occur, if i then on the TS server only starts (doubleclick) on the RemoteApp Manager under  Administrative tools - Remote Desktop Services then it takes some time before the programs open, but when it opens it shows a grey box with something like connecting to local host, and when that box dissapear and the RemoteApp Manager starts up then the icons on the rdweb on RD server is showing and working. After some search on google i see that there are lots of this type of problems and that there isnt any solution to it. But since its enough to start the RemoteApp Manager program on the TS server, what does that program do and is there any services that is restarted when starting that program or is it possible to add something in the Task Scheduler to start and stop that program once a day?

Hi everybody,

I have an issue that has been cracking my mind..

A few years ago I configured a server for one of my customers, it's a Server 2008R2 with the RDS server role.

It has been working like a charm for years,,

This is what's going on.. (all of the problems exist while a user is logged-on to a RDP session).

In the AD is a container with a few users that have some extra rights through a GPO.

These users have administrator rights(member of the builtin admin), and rights to start the task-manager to send messages to other users.

All of a sudden these users are no longer able to send messages, they are able to open the taskmanager but a soon as they try to send a message, it says access denied.

The builtin administrator can still send these messages.

I tried creating a new user and the same issue appears.

I checked the date when the last modification have been made on any GPO but the last change was about a year ago.
So nothing changed in the user rights or GPO's.

An other issue that occurs is when a user opens a browser session(IE) and needs to browse the server to (for example) upload a file, it suddenly starts asking for credentials on the shares.
But when the user opens a share through the windows explorer, it works fine.

The browser doesn't start in any special way, just a simple users session.

The event viewer doesn't display any information that has anything to do with these issues.

This all started about 2 weeks ago.

Any ideas?

With kind regards,

Tim Grave

Hi,

I tried to install remote desktop services in window server 2012, I joined my current domain ( in window server 2003).

During installation, it require me to promote my server to domain controller? This is one of the requirement for remote desktop services?

If I didnt join any domain, it prompt me I must join a domain.

Anyone can advise me? provide me a steps by steps guide will be perfect!

Thanks 

We have setup a Windows Server 2012 R2 Std running Remote Desktop Services (workgroup server), and allow access only by VPN.

During setup of the RDS, as I recall, I was not able to install licensing unless I also installed a security certificate.

I purchased a standard SSL through GoDaddy, installed same on this server, but now wonder if I made a mistake in doing so.

Since this server is behind a firewall and not available on the Internet, would a self-signed certificate suffice? Or do I even need to install a SSL?

Thanks for any help in advance,

Robb

Hi,

 Is it possible to use URL redirection with RemoteApp for RDS 2012 so that a link opened on an RDSH server is actuallly opened using the local client browser?

Thanks,
Dan

Hi,

I am having an issue on a Windows Server 2008 R2 RDS. When using a couple of third-party programs which try to restore from backup, the program appears to crash. Below are the steps which occur:

1. Open third-party program

2. Go to restore file from backup

3. Click on 'Browse' button

4. Program crashes

I am able to replicate this issue with 2 different third-party programs, from 2 different vendors.

What both situations have in common, is that when clicking on browse, Windows (explorer) is trying to look for a .zip file, which will then restore to specified location. Both programs use the native Windows extractor to extract the file (well at least they would if the program wouldn't crash).

The issue occurs for all users, including administrator. The RDS Server does have 7-zip installed, but uninstalling this does not resolve the issue. There are no other third-party zip programs on the server.

Hi Everyone,

Hopefully this is the right place to post. Have searched quite a bit through the forums (not all 19000+ pages though), and can't seem to find a similiar issue.

I have also searched the internet and tried all solutions others with a similiar problem have.

This is my problem:

We have two servers running Server 2008 R2, set up as Remote Desktop Servers in a cluster setup.

The session broker is located on the second server (This is an active server which has sessions load balanced to it). There is also a DNS round robin setup

Problem: When sessions are allowed to be load balanced on Server2, then the users cannot connect to the cluster. The round robin seems to still send some sessions to the first server, and these seem to connect fine.

I suspected the issue was with the WMI Respository, and so started. I found a lot of errors, but have been unable to fix them.

I downlaoded the WMIDiag from Microsoft, and here is the report:

48866 15:56:44 (0) ** WMIDiag v2.1 started on 15 April 2015 at 15:48.
48867 15:56:44 (0) **
48868 15:56:44 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
48869 15:56:44 (0) **
48870 15:56:44 (0) ** This script is not supported under any Microsoft standard support program or service.
48871 15:56:44 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
48872 15:56:44 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
48873 15:56:44 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
48874 15:56:44 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
48875 15:56:44 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
48876 15:56:44 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
48877 15:56:44 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
48878 15:56:44 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
48879 15:56:44 (0) ** of the possibility of such damages.
48880 15:56:44 (0) **
48881 15:56:44 (0) **
48882 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48883 15:56:44 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
48884 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48885 15:56:44 (0) **
48886 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48887 15:56:44 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'MIBCO\CONN.LOMBARD' on computer 'SSCRDS02'.
48888 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48889 15:56:44 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
48890 15:56:44 (0) ** INFO: => 3 possible incorrect shutdown(s) detected on:
48891 15:56:44 (0) **          - Shutdown on 05 December 2014 22:55:28 (GMT-0).
48892 15:56:44 (0) **          - Shutdown on 12 December 2014 06:43:00 (GMT-0).
48893 15:56:44 (0) **          - Shutdown on 27 February 2015 05:19:26 (GMT-0).
48894 15:56:44 (0) **
48895 15:56:44 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
48896 15:56:44 (0) ** Drive type: ......................................................................................................... SCSI (DELL PERC H700 SCSI Disk Device).
48897 15:56:44 (0) ** There are no missing WMI system files: .............................................................................. OK.
48898 15:56:44 (0) ** There are no missing WMI repository files: .......................................................................... OK.
48899 15:56:44 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
48900 15:56:44 (0) ** AFTER running WMIDiag:
48901 15:56:44 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
48902 15:56:44 (0) ** - Disk free space on 'C:': .......................................................................................... 297281 MB.
48903 15:56:44 (0) **   - INDEX.BTR,                     5513216 bytes,      2015/04/15 03:52:21 PM
48904 15:56:44 (0) **   - MAPPING1.MAP,                  76804 bytes,        2015/04/15 03:50:51 PM
48905 15:56:44 (0) **   - MAPPING2.MAP,                  76804 bytes,        2015/04/15 03:52:21 PM
48906 15:56:44 (0) **   - OBJECTS.DATA,                  22036480 bytes,     2015/04/15 03:52:21 PM
48907 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48908 15:56:44 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
48909 15:56:44 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
48910 15:56:44 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
48911 15:56:44 (0) ** => This will prevent any WMI remote connectivity to this computer except
48912 15:56:44 (0) **    if the following three inbound rules are ENABLED and non-BLOCKING:
48913 15:56:44 (0) **    - 'Windows Management Instrumentation (DCOM-In)'
48914 15:56:44 (0) **    - 'Windows Management Instrumentation (WMI-In)'
48915 15:56:44 (0) **    - 'Windows Management Instrumentation (ASync-In)'
48916 15:56:44 (0) **    Verify the reported status for each of these three inbound rules below.
48917 15:56:44 (0) **
48918 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' GROUP rule: ............................................. ENABLED.
48919 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... ENABLED.
48920 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ ENABLED.
48921 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... ENABLED.
48922 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. ENABLED.
48923 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48924 15:56:44 (0) ** DCOM Status: ........................................................................................................ OK.
48925 15:56:44 (0) ** WMI registry setup: ................................................................................................. OK.
48926 15:56:44 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
48927 15:56:44 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
48928 15:56:44 (0) ** - SMS Agent Host (CCMEXEC, StartMode='Automatic')
48929 15:56:44 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
48930 15:56:44 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
48931 15:56:44 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
48932 15:56:44 (0) **          this can prevent the service/application to work as expected.
48933 15:56:44 (0) **
48934 15:56:44 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
48935 15:56:44 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
48936 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48937 15:56:44 (0) ** WMI service DCOM setup: ............................................................................................. OK.
48938 15:56:44 (0) ** WMI components DCOM registrations: .................................................................................. OK.
48939 15:56:44 (0) ** WMI ProgID registrations: ........................................................................................... OK.
48940 15:56:44 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
48941 15:56:44 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
48942 15:56:44 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
48943 15:56:44 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
48944 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48945 15:56:44 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
48946 15:56:44 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
48947 15:56:44 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
48948 15:56:44 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
48949 15:56:44 (0) **         selecting 'Run as Administrator'.
48950 15:56:44 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
48951 15:56:44 (0) **         in the Task Scheduler within the right security context.
48952 15:56:44 (0) **
48953 15:56:44 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
48954 15:56:44 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
48955 15:56:44 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
48956 15:56:44 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
48957 15:56:44 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
48958 15:56:44 (0) **
48959 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
48961 15:56:44 (0) **        - ACTUAL ACE:
48962 15:56:44 (0) **          ACEType:  &h0
48963 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
48964 15:56:44 (0) **          ACEFlags: &h4
48965 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
48966 15:56:44 (0) **          ACEMask:  &hB
48967 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
48968 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
48969 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
48970 15:56:44 (0) **        - EXPECTED ACE:
48971 15:56:44 (0) **          ACEType:  &h0
48972 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
48973 15:56:44 (0) **          ACEFlags: &h0
48974 15:56:44 (0) **          ACEMask:  &h1F
48975 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
48976 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
48977 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
48978 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
48979 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
48980 15:56:44 (0) **
48981 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
48982 15:56:44 (0) **    This will cause some operations to fail!
48983 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
48984 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
48985 15:56:44 (0) **
48986 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
48987 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\INTERACTIVE' DOES NOT match corresponding expected trustee rights (Actual->Default)
48988 15:56:44 (0) **        - ACTUAL ACE:
48989 15:56:44 (0) **          ACEType:  &h0
48990 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
48991 15:56:44 (0) **          ACEFlags: &h4
48992 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
48993 15:56:44 (0) **          ACEMask:  &hB
48994 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
48995 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
48996 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
48997 15:56:44 (0) **        - EXPECTED ACE:
48998 15:56:44 (0) **          ACEType:  &h0
48999 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
49000 15:56:44 (0) **          ACEFlags: &h0
49001 15:56:44 (0) **          ACEMask:  &h1F
49002 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
49003 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
49004 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
49005 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
49006 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
49007 15:56:44 (0) **
49008 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
49009 15:56:44 (0) **    This will cause some operations to fail!
49010 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
49011 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
49012 15:56:44 (0) **
49013 15:56:44 (0) **
49014 15:56:44 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
49015 15:56:44 (0) ** DCOM security error(s) detected: .................................................................................... 2.
49016 15:56:44 (0) ** WMI security warning(s) detected: ................................................................................... 0.
49017 15:56:44 (0) ** WMI security error(s) detected: ..................................................................................... 0.
49018 15:56:44 (0) **
49019 15:56:44 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
49020 15:56:44 (0) ** Overall WMI security status: ........................................................................................ OK.
49021 15:56:44 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
49022 15:56:44 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 5.
49023 15:56:44 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
49024 15:56:44 (0) **   'select * from MSFT_SCMEventLogEvent'
49025 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49026 15:56:44 (0) **   'SELECT * FROM __NamespaceCreationEvent'
49027 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49028 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_EmbeddedObject"'
49029 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49030 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_Config"'
49031 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49032 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy"'
49033 15:56:44 (0) **
49034 15:56:44 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
49035 15:56:44 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
49036 15:56:44 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
49037 15:56:44 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
49038 15:56:44 (0) ** - ROOT/SERVICEMODEL.
49039 15:56:44 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
49040 15:56:44 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
49041 15:56:44 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
49042 15:56:44 (0) **    i.e. 'WMIC.EXE /NODE:"SSCRDS02" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
49043 15:56:44 (0) **
49044 15:56:44 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
49045 15:56:44 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
49046 15:56:44 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 34 ERROR(S)!
49047 15:56:44 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49048 15:56:44 (0) **   MOF Registration: ''
49049 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49050 15:56:44 (0) **   MOF Registration: ''
49051 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49052 15:56:44 (0) **   MOF Registration: ''
49053 15:56:44 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49054 15:56:44 (0) **   MOF Registration: ''
49055 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49056 15:56:44 (0) **   MOF Registration: ''
49057 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49058 15:56:44 (0) **   MOF Registration: ''
49059 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49060 15:56:44 (0) **   MOF Registration: ''
49061 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49062 15:56:44 (0) **   MOF Registration: ''
49063 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49064 15:56:44 (0) **   MOF Registration: ''
49065 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49066 15:56:44 (0) **   MOF Registration: ''
49067 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49068 15:56:44 (0) **   MOF Registration: ''
49069 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49070 15:56:44 (0) **   MOF Registration: ''
49071 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49072 15:56:44 (0) **   MOF Registration: ''
49073 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49074 15:56:44 (0) **   MOF Registration: ''
49075 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49076 15:56:44 (0) **   MOF Registration: ''
49077 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49078 15:56:44 (0) **   MOF Registration: ''
49079 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49080 15:56:44 (0) **   MOF Registration: ''
49081 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49082 15:56:44 (0) **   MOF Registration: ''
49083 15:56:44 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49084 15:56:44 (0) **   MOF Registration: ''
49085 15:56:44 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49086 15:56:44 (0) **   MOF Registration: ''
49087 15:56:44 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49088 15:56:44 (0) **   MOF Registration: ''
49089 15:56:44 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49090 15:56:44 (0) **   MOF Registration: ''
49091 15:56:44 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49092 15:56:44 (0) **   MOF Registration: ''
49093 15:56:44 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49094 15:56:44 (0) **   MOF Registration: ''
49095 15:56:44 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49096 15:56:44 (0) **   MOF Registration: ''
49097 15:56:44 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49098 15:56:44 (0) **   MOF Registration: ''
49099 15:56:44 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49100 15:56:44 (0) **   MOF Registration: ''
49101 15:56:44 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49102 15:56:44 (0) **   MOF Registration: ''
49103 15:56:44 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49104 15:56:44 (0) **   MOF Registration: ''
49105 15:56:44 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49106 15:56:44 (0) **   MOF Registration: ''
49107 15:56:44 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49108 15:56:44 (0) **   MOF Registration: ''
49109 15:56:44 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49110 15:56:44 (0) **   MOF Registration: ''
49111 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49112 15:56:44 (0) **   MOF Registration: ''
49113 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49114 15:56:44 (0) **   MOF Registration: ''
49115 15:56:44 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
49116 15:56:44 (0) **    a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
49117 15:56:44 (0) **    You can refresh the WMI class provider buffer with the following command:
49118 15:56:44 (0) **
49119 15:56:44 (0) **    i.e. 'WINMGMT.EXE /SYNCPERF'
49120 15:56:44 (0) **
49121 15:56:44 (0) ** WMI MOF representations: ............................................................................................ OK.
49122 15:56:44 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
49123 15:56:44 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
49124 15:56:44 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
49125 15:56:44 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
49126 15:56:44 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49127 15:56:44 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49128 15:56:44 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
49129 15:56:44 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49130 15:56:44 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49131 15:56:44 (0) **
49132 15:56:44 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
49133 15:56:44 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
49134 15:56:44 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
49135 15:56:44 (0) ** WMI static instances retrieved: ..................................................................................... 6304.
49136 15:56:44 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
49137 15:56:44 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 3.
49138 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49139 15:56:44 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
49140 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
49141 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
49142 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
49143 15:56:44 (0) **
49144 15:56:44 (0) ** # of additional Event Log events AFTER WMIDiag execution:
49145 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
49146 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
49147 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
49148 15:56:44 (0) **
49149 15:56:44 (0) ** 34 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
49150 15:56:44 (0) ** => This error is typically a WMI error. This WMI error is due to:
49151 15:56:44 (0) **    - a missing WMI class definition or object.
49152 15:56:44 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
49153 15:56:44 (0) **      You can correct the missing class definitions by:
49154 15:56:44 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
49155 15:56:44 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
49156 15:56:44 (0) **            (This list can be built on a similar and working WMI Windows installation)
49157 15:56:44 (0) **            The following command line must be used:
49158 15:56:44 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
49159 15:56:44 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
49160 15:56:44 (0) **            with WMI by starting the ADAP process.
49161 15:56:44 (0) **    - a WMI repository corruption.
49162 15:56:44 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
49163 15:56:44 (0) **      to validate the WMI repository operations.
49164 15:56:44 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
49165 15:56:44 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
49166 15:56:44 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
49167 15:56:44 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
49168 15:56:44 (0) **      the WMI repository must be reconstructed.
49169 15:56:44 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
49170 15:56:44 (0) **          otherwise some applications may fail after the reconstruction.
49171 15:56:44 (0) **          This can be achieved with the following command:
49172 15:56:44 (0) **          i.e. 'WMIDiag ShowMOFErrors'
49173 15:56:44 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
49174 15:56:44 (0) **          ALL fixes previously mentioned.
49175 15:56:44 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
49176 15:56:44 (0) **
49177 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49178 15:56:44 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
49179 15:56:44 (0) ** INFO: Unexpected registry key value:
49180 15:56:44 (0) **   - Current:  HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
49181 15:56:44 (0) **   - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
49182 15:56:44 (0) **     From the command line, the registry configuration can be corrected with the following command:
49183 15:56:44 (0) **     i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
49184 15:56:44 (0) **
49185 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49186 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49187 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49188 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49189 15:56:44 (0) **
49190 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49191 15:56:44 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
49192 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49193 15:56:44 (0) **
49194 15:56:44 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\CONN.LOMBARD\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_SSCRDS02_2015.04.15_15.48.25.LOG' for details.
49195 15:56:44 (0) **
49196 15:56:44 (0) ** WMIDiag v2.1 ended on 15 April 2015 at 15:56 (W:110 E:41 S:1).

This seems to be the biggest problem:

48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)

This seems to be the second biggest error (and there are a few of them):

0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.

I have tried:

winmgmt /resyncperf

winmgmt /verifyrepository

winmgmt /salvagerepository

winmgmt /resetrepository

I have also tried registering the mof files with

MOFCOMP <FileName.mof>

Lastly, I even disabled the WMI service, renamed the Repository folder, and had it rebuild the repository.

I got stuck on re registering the 'NT AUTHORITY\SYSTEM' (I think it is in the Components section in Administrative tools), as I could not find clear instructions on exactly how to go about it.

Chkdsk found no errors

Sfc /scannow found no errors

winmgmt /verifyrepository finds no errors.

I'm hoping someone here might be able to steer me in the right direction to get this resolved, as I do not want to rebuild a server that hosts a connection broker and has over 100 user profiles on it, as well as some very annoying and finniky LOB apps installed, which will have to manually be reinstalled for each profile.

I have a problem with a 6 server deployment is unable to be managed from Server Manager. When you bring up the Remote Desktop Services section, it will show all servers online however no collections or servers are shown in the other two windows.  It seems to be refreshing the panes however it never stops.  This can be replicated on multiple other servers.  Issue is possible the connection broker?  Also, deployment seems to be fine when managed via powershell.  All roles show correctly and all collections are functioning correctly.  Only seems to be a Server Manager issue with the Remote Desktop Servers module on the Connection Broker.   Any ideas?  Thank!

-Matt

I am having an issue with the configuration on RD Web Access so that our RemoteApp Programs configured are accessible.

RDS01 - RD Session Host

RDG01 - RD Gateway, RD Web

So I logon to RD Web and enter the Configuration screen and when I enter RDS01 I get the above message. If I was to leave it as localhost, my understanding is that it would use RDG01 - is that correct.

I have discovered recently that a Public user account and related folders has been created on my pc. the result has been thatprograms were installed on this folder and corrupted the structure of the program (DAZ Studio 3D) and with their support we had to reinstall all the programs and 97 addons! Nvidia creates UPDATUSUSER Accounts for their drivers update without the user knowing it or being able to control its access.

This is outrageous and a felony concerning the confidentiality international laws on the internet .

I want this user account and folder eradicated from my pc.

Windows is not authorized in any way to create without my strict consent an account on my pc that I cant manage.I have never had in the past in previous versions of Windows such an account and will not accept it whatever new versions of windows I use;

How can I suppress the account and related folders as again some installed programs have gone there

Thanks

CLaude ROZSA- Paris- France

Ps your desk on the hotline in France was unable to solve the problem which obviously they are not aware of.

Hello i have a question about moving my C:\users profiles.

My current settings on the servers are:

AD-Server 2012

SQL-Server 2012

TS- server with RDS roles (RDwebacces, RDs broker, RD session host) 2012

everything about user profiles is now in C:\Users

My new settings for the server will be:

AD-ActiveDirectory - server

SQL-Server

TS1- RDS (RDwebacces, broker, RDS server group management) 2012R2 (I have enabeld userProfileDisks to Filesistem server)

TS2- RDS(Session host) load balance 2012R2

TS3- RDS (Session host) load balance 2012

FileSistem - server ( here i will have on E: partition the new functionality UserProfileDisks) 2012R2

So is there a way to move profiles from TS - C:\Users to FileSistem - E:\UserProfileDisks

I am new to this so any idea wil be helpful.

Has anyone a solution to this problem of the sound just dropping out of a RDP connection after a day or two?

Win Server2008 (32 bit) running as a Terminal Server.

WIN 7 Clients (32 bit)

Sound is absolutely critical on the program being ran on the WIN7 clients when connecting via RDP to the Server 24/7.

But the sound just stops working on the RDP clients after a day or two.

If I minimize the RDP session and try the sound from the native windows session it works, but sound is not working within the RDP session.

and it takes a restart of the RDP session to restore sound, but then aftera day or two I get a call to say the sound is no longer working- a restart of the RDP sessions restores the sound.

I have checked the Environment sound settings in the RDP setup on the clients and have them set to play on the client, and I have checked that sound is not disabled in the Terminal Server end of things for RDP sessions.

I would really appreciate to help with this if anyone has suggestions.