RD Session Host connections don't appear on License Manager

We have setup a Server 2012 R2 RDS deployment with remote-site RD Host Servers all pulling CALs from a central RD License Server. I am able to RDP five sessions into the first RD Session Host Server OK, and the RD License Diagnoser says all is well with
the connection to the license server. However I am not seeing any licenses being issued by the central License Server for those five test users, even after a Refresh. The five test users are local to the RD Session Host Server, and not in AD. Do local accounts
not show up in the License Server's RD Licensing Manager screen?  Do they not require the RD Session Host to 'pull' CALs from the License Server?  I am thinking I should be seeing the licenses being distributed to the five users and am concerned
that I do not.
License Server 2012 R2 - Per User CALs - Joined to Active Directory
RD Host Server #1 with the five RDP sessions is 2012 R2 - Joined to Active Directory
Thanks in advance for any insights! 

Hi Jim,
Thanks for your comment.
Initially would like to share that “Per User CAL tracking and reporting is not supported in workgroup mode”, in workgroup mode we can only install RDS Device CAL but as you have domain joined with Per User CAL is ok. But RDS per User CAL can’t be used\tracked
by local user account. 
http://support.microsoft.com/kb/2473823
You can use following script to check which user got logged in.
Get-LoggedOnUser Gathers information of logged on users on remote systems
https://gallery.technet.microsoft.com/scriptcenter/Get-LoggedOnUser-Gathers-7cbe93ea
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Similar Messages

  • [Forum FAQ] Troubleshoot the error "The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode"

    Symptom
    RD License server is a key component of RDS. It licenses users to access RDS servers.
    After purchase the required RDS CALs, we need to activate the RDS License server and install the purchased RDS CALs. However, during the installation or after installation, we may face errors
    about RDS License.
    In most cases, the following error may occur.
    Error:
    The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server "Server name" does not have any installed licenses with the following
    attributes:
    Product version: Windows Server 2012
    Licensing mode: Per User
    License type: RDS CALs
    Troubleshooting
    1. Check whether the RD License Configuration is configured properly and there are no Warnings in the Event.
    2. The License Server should be part of 'RD Server License' group in Active Directory Domain Services.
    3. Check if the Licensing Mode is correct.
    - To change the Licensing Mode we can use RD Licensing diagnose, PowerShell cmdlet and Group Policy.
    Via PowerShell cmdlet:
    To change the licensing mode on RDSH/RDVH:
    $obj = get-wmiobject -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
    $obj.ChangeMode(value)
    # Value can be 2 - per Device, 4 - Per user
    Via Group Policy
    Path: Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
    Use the specified RD license servers = FQDN of server name
    Set the Remote Desktop licensing mode =
    Per User
    However, if issue persists, please provide detailed information and post the question in the
    Remote Desktop Services (Terminal Services) forum.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi Richard,
    You need to uninstall Remote desktop session host feature. After removing it, you will default two connections which does not need to purchase RD CALs'.
    Thanks,
    Umesh.S.K

  • Point the remote desktop session host VM from Azure to a license server located in DMZ (on-prem) by not using s2s or p2s.

    Hi All,
    Good day. I am just new in azure and still testing some IaaS features and services. May I ask if it is possible to point the remote desktop session host VM from Azure to a license server located in DMZ (on-prem) by not using s2s or p2s? If yes, may I ask
    if how can this be achieve?
    Hoping for your advise.
    Thanks,
    Sebastian Jose

    Hello Manu,
    Good day. Thanks for the reply. DMZ is on prem.
    Thanks,
    Glenn Jose

  • Point Remote Desktop Session Host VMs from Azure to a License Server located in DMZ

    Hi All,
    Good day. I am just new in azure and still testing some IaaS features and services. May I ask if it is possible to point the remote desktop session host VM from Azure to a license server located in DMZ not using s2s or p2s? If yes, may I ask if how can this
    be achieve?
    Hoping for your advise.
    Thanks,
    Glenn Jose

    Hello Manu,
    Good day. Thanks for the reply. DMZ is on prem.
    Thanks,
    Glenn Jose

  • Server 2012 R2 RDS- Only want the Session Host, Connection Broker and Licensing Server!

    Hi all,
    Wondering if anyone has experience with implementing Remote Desktop Services (RDS) on Windows Server 2012 R2.
    I am doing an RDS design for a platform where we only need an RDS Session Host, Licensing Server and Connection Broker. We do not need web access as these servers will simply be jump boxes internally!
    However, implementing this correctly in our test environment has proved to be tricky. The options are:
    Use the Server Manager and do a traditional install via Roles and Features ( specifically add the Session Host, Licensing Server and Connection Broker). The installation process seems to go through ok in this scenario but when I head over to the Remote
    Desktop Services section of the Server Manager I simply get the message 'An RDS Deployment does not exist in the server pool. To create a deployment head to Roles and Features'.
    Use the specific ‘Remote Desktop Services installation’ option on the Server Manager and do a Session Based Desktop deployment and Quick Start. This installation process seems to go through correctly and the Remote Desktop Section seems to be working
    correctly via the Server Manager. However this process is ‘hard locked’ i.e. it installs the session host, web access and connection broker. I can then remove the web access component later from Roles/ Features.
    Is there a best practice (if any) for installation? i.e. Will there be any issues down the line if I remove RDS Web Access from my server while following method 2?
    There is a complete lack of documentation from Microsoft here so not sure what to do! Just need a basic RDS session based deployment.

    Hi,
    As I know from server 2012\R2 the best deployment skill is to perform via “Remote Desktop Services” installation mode with Standard deployment and don’t let single role to install. Because when we install through RDS mode, there are specific extra tools and
    services activated along with that deployment which you can’t find with single role installation. And that is for sure, when we install RDS role as of this, by default we will get install RDCB, RDSH and RDWA role installed.
    Sorry don’t have any option to try to remove that role as that role basically needed for RemoteApp and Desktop purpose. But if you want then you can try it with help of “Remove-RDServer”Powershell command.
    https://technet.microsoft.com/en-us/library/jj215506.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    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]

  • Windows Components/remote desktop services/remote desktop session host/profile doesn't appear to be working on 2008R2 boxes

    I have two domains.   One is an account domain with a one way trust with the resource domain.   Resource domain trusts the account domain and has a number of 2008R2 servers running within.  I am experiencing severe logon delays
    due to these servers being unable to access the server that hosts the user home folder specified directly on the user account profile tab from the account domain.   When using my workstation in the actual account domain (corporate) I have no
    problems.
    Because of these network restrictions,  I need to override the 2008R2's desire to access that user home folder location in the account domain.
    So far the best thing I have found to try is Windows Components/remote desktop services/remote desktop session host/profile/Set Remote Desktop User Home Directory
    The problem is that so far I have tried to configure this to point to both a local folder as well as a network path and it doesn't appear to be doing anything.   Not seeing any errors in the app or system log either.
    It is still trying to map the path in the account domain.
    Any ideas?
    Is there a better way to accomplish my goal?   The servers in the resource domain will be Citrix servers and there will be a lot of users connecting from the account domain.
    I tried this setting too,  but it only seems to work on the 2012 machines in my Resource domain.
    With the introduction of Windows 8 and Windows Server 2012 there is now a new group policy setting called “Set user home folder” and is found under Computer Configuration > Policies > Administrative Templates > System > User Profiles
    Help!

    Hi,
    This might be due to permission problems. Please check whether the user accounts for whose home folder to be redirected have permissions in the shared folder specified in the server. 
    Checkout the below link on Best Practice for creating Roaming Profile and Folder Redirection
    http://www.grouppolicy.biz/2010/08/best-practice-roaming-profiles-and-folder-redirection-a-k-a-user-virtualization/
    Regards,
    Gopi
    JiJi
    Technologies

  • Changing RemoteApp Session Host connection name in 2012

    I am looking for a way to change the server name you connect to (on the Session Host), like you could in 2008 R2. Pictures a worth a thousand words, so I've attached a picture of exactly what I am looking for:
    The servers are setup so their names are servername.domain.local, but since they will be facing outwards (with a RD Gateway between them, of course) and non-domain members will be accessing them, we need a way to change the "server name" to servername.domain.com
    (.dk actually, but you get the point), so the certificate applies to it.
    Currently, connecting looks like this:
    We don't want our customers getting this dialog box. Any help is appreciated.

    Hi,
    The architecture is changed.We don't use the DNS RR or NLB to redirect the initial connection any more.We just need the RDCB database to redirect the connection.The process is simplified.In short, there is no need to change the server name like the above.All
    the changeable settings are on the RDCB.To get dialog box disappeared,you need to change the cert name to match the destination computer.
    Regards,
    Clarence
    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback on our support quality, please send your feedback
    here.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Onscreen Keyboard appears when shadowing session on 2012R2 Remote Desktop Session Host

    As the title suggests, whenever I shadow a session on our 2012R2 RDSH server, the onscreen keyboard appears.  The taskbar also unlocks.
    Both of these behaviours mean that the user can tell when their session is being shadowed, which I don't always want to be the case - sometimes I want to be able to monitor the session without their knowledge.
    Anyone know how I can stop this from happening?

    Hi,
    Thank you for posting in Windows Server Forum.
    Yeah, we can use the following command where we can take user shadow session without giving him any notification, and no need to approve by the user.
    mstsc.exe /shadow:ID /v:ServerName /control /noConsentPrompt
    But for this, we need to set the following group policy:
    [Computer Configuration | User Configuration]
    \Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections
    Set rules for remote control of Remote Desktop Services user sessions:  Enable
    Select the option: Full Control without User’s permission
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Using Windows Server 2012 per-User RDS CAL on Server 2008 R2 Session Host

    I have a Remote Desktop Licensing Server setup on my domain controller running Windows Server 2012 R2. I have installed a
    ’Windows Server 2012 Remote Desktop Services per-User CAL’ there and activated the licensing server already.
    Currently I use ONLY Windows Server 2008 R2 machines as RDS Session Hosts (in the future I plan to transition them to 2012 R2, hence the CAL I bought is
    already in the newest version).
    I have already configured my WS 2008 RDS Session Hosts: set
    Per-User licensing mode and specified license server address. The connectivity between my Session Host(s) and my License Server seems to be ok as the
    Remote Desktop Session Host Configuration window on the Session Host correctly lists the 2012 per-user
    license (CAL installed on server) from the license server.
    On the License Server I can also see event logs entries (in
    Microsoft-Windows-TerminalServices-Licensing/Admin), indicating that the user has been issued a license.
    The issue I am having is that the license being issued is
    2008 Per User CAL license (Build-in OverUsed - temporary) and not the 2012 Per User CAL license which is the only license installed on the server. According to the RDS CAL interoperability matrix at
    social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx, I was expecting the 2012 license to be backward-compatible with 2008 client (and that
    in the absence of legacy licenses, the (only) 2012 license would be used for all clients connecting to the licensing server)
    Before I bought my license, I found this document: 
    download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/WindowsServerRDS_VLBrief.pdf 
    which says that - "newer version RDS CALs can be used with an older version of the server software" (In section FAQ, Q4), which means to me that
    the 2012 license would work as-is for the 2008 Server and gives me flexibility when upgrading to the new server version.
    How can I make this CAL work in my environment? 
    Note:
    I have already explicitly disabled
    Prevent license upgrade Group Policy setting which I assumed would fix the issue but nothing has changed.
    Then I have enabled License server security group Group Polity setting
    and added computers from my domain to RDS Endpoint Servers AD group. I have also created new AD group called
    Terminal Server Computers and added the computer accounts there, but it changes
    nothing. Reference - technet.microsoft.com/en-us/library/ee791761.aspx , technet.microsoft.com/en-us/library/cc725704.aspx and blogs.msdn.com/b/rds/archive/2009/09/17/control-the-issuance-of-rds-cals.aspx.
    I found one potential ‘workaround’ which involved manually downgrading my CAL license by calling
    Microsoft Clearinghouse. I am very reluctant do to so because, as I upgrade parts of my infrastructure to Server 2012, I’d need to then ask Microsoft to manually upgrade a part of my license back as well.
    Am I missing something? What should I do to get my 2012 CAL to be issued to 2008 R2 server

    Hi, I have tried several other possibilities.
    I change expire date for my temporary assigned license (2008 CAL overused). It can be done, by changing Active Directory user properties – msTSExpireDate. When I restart my Session Host server and logged again, my license was renewed
    for next 60 days (event ID - 4145).
    I also delete information about license for this user (clear msTSExpireDate and msTSLicenseVersion). And the license was successfully removed from License Manager. After another SH restart it gets the same – 2008 overused – license
    (event ID 4143 - license server has successfully issued …)
    I now, that changing info in AD attributes is a little trick, and this is not a real value - only a reference, but it was useful to delete or change expiration date of license. But it didn’t change type of license as I expected.
    Reference -
    http://discussions.citrix.com/topic/243320-windows-2008-licensing-questions/
    To TP:
    I have found your post with information:
    If you have a Server 2012 RD Licensing server you may install your 2012 RDS CALs on it (no downgrade necessary) and then set your Server 2008 R2 RDSH to
    use the 2012 RDL server.  The 2012 RD Licensing server will automatically issue the CALs as 2008. -
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/6046ded1-96bf-4d79-89ce-38aac2a6694e/can-we-use-windows-server-2012-rds-cal-license-in-rds-2008-r2-server?forum=winserverTS
    And it showing my situation in brief. I also found
    similar problems, but the solutions don’t meet my expectations.
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/dcfb1966-89a8-4b5d-bf5a-ff03ac0b7a66/rds-cal-licenses-not-recognized?forum=winserverTS
    – “sudden all of the CALS were available”
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/f1228599-8452-4a3e-a263-061de14bfcfe/server-2012-rds-builtin-overused-cals-issue?forum=winserverTS
    – “this should go away after a while”
    Is there a way to determine this time you mentioned before? Or should I just wait patiently…

  • RD session host is not detecting the license

    My RD session hosts are not able to recognize the RDS CALs. Here is my setup:
    License Server :
    Windows 2012 Server (workgroup), running on Amazon cloud
    No. of license: 20
    License activation is done.
    RD session host server:
    Windows 2008 R2 (workgroup), running on Amazon cloud
    Can connect to license server on port 135
    License server is added in the RD session host
    Licensing Diagnosis under RD session host detects the License server fine and give positive report. (Screenshot attached)
    Few other settings:
    These are user based CALs.
    Firewall is disabled on the license server
    As this is in workgroup, the Administrator's password on license server and on RD session host server is same. (else the license diagnosis will fail).
    ISSUE:
    Even though RD session host is detecting the license server fine as well as the licensing diagnosis gives a positive report, I get the typical balloon pop up saying "RDP connection will be lost after 119 days... " (the typical message it shows
    when you do not have RD session host license.)
    What Am I missing here. Any pointers would of great help. 

    Hi,
    Thank you for posting in Windows Server Forum.
    You need to contact MS Clearinghouse with you all license related documents and numbers with all paper in hand and explain them the scenario they will help you. Below links helps to locate the MS clearing house.
    Locate the Microsoft Clearinghouse Telephone Number for Your Country or Region
    More information:
    Switching Between Device and User CALs
    This statement “RDS Host and RDS licensing server roles can both be installed on the same server” indicates that you can install RDSH and RDLS on same server. In addition, RDS server 2012 required RD Licensing Server 2012. But
    yes, you can install server 2012 RD Licensing Server and associate your RDS CAL’s on it and let’s your RD Session Host server works on server 2008 R2. 
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • The grace period for the Remote Desktop Session Host server has expired

    <p>I'm running Windows Server 2012, we only have 1 server and it's a DC.  I'm trying to RD to the server from my Windows 7 laptop. It was working fine on Friday but when I came in on Monday I got message saying that 'The remote session was disconnnected
    because there are no Remote Desktop License Servers available to provide a license'
    So after a bit of digging I found out my 'grace period' had expired, so ordered a new license which I got today, installed this all ok but still i cannot connect via RD I get the same message....went into the RD License Diagnoser and it said the problem
    was as follows
    'The grace period for the Remote Desktop Session Host server has expired, but the RD Session Host server has not been configured with any license servers. Connections to the RD Session Host server will be denied unless a license server is configured for
    the RD Session Host server.'
    Suggested Resolution as follows
    Configure a license server for the Remote Desktop Session Host server. If you have an existing license server, specify that license server for the RD Session Host Server. Otherwise, install RD Licensing on a computer on your network and Configure RD Session
    Host Server to use it.'
    I cannot figure out how to do this as I cannot find the RD Session Host Server tool. 
    Can any of you lovely people help me please

    Hello,
    Best option would be to assign the license server by using AD GPO. Youl will need to configure the following:
    Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing
    and define the settings for:
    Use the specified Remote Desktop License Server
    Set the Remote Desktop Licensing mode
    Then assign the policy tho your server.
    regards Robert Maijen

  • The Remote Desktop Session Host server is within its grace period Question

    On my Windows 2012 Server, when I open the RD Licensing Diagnoser, I see this:
    The Remote Desktop Session Host server is within its grace period, but the RD Session Host server has not been configured with any license server.
    Configure a license server for the Remote Desktop Session Host server. If you have an existing license server, specify that license server for the RD Session Host server. Otherwise, install RD Licensing on a computer on your network and Configure RD Session
    Host server to use it.
    I have a few questions.  First, I have 10 virtual machines setup (all Windows 7 Enterprise).  I have my 10 VDI licenses for those machines.  Do I need another license for my Remote Desktop Session Host?  If not, how do I license my RD Session
    Host Server?  If so, does anyone know how much they cost?  I have no licensing server.  I just have my Windows 2008 server that is my AD and DNS Server (where my GPO's sit too) and my Windows 2012 server that is dedicated to only running VM's
    for the remote users.

    you should probably speak to a licensing expert as it can start getting fairly complicated and we wouldn't want to advise you incorrectly. Generally if you speak to a LAR (Large Account Reseller) they should be able to provide the guidance you need. 
    You can find more information on licensing virtual desktop through this white paper
    Licensing
    Microsoft's Virtual Desktop Infrastructure Technology
    Regards,
    Denis Cooper
    MCITP EA - MCT
    Help keep the forums tidy, if this has helped please mark it as an answer
    My Blog
    LinkedIn:

  • Relation between RD Connection broker and RD session host farm in 2012 R2

    Good Day
    I have configured standard RDS session based deployment recently on 2012 R2 servers
    Everything is working as expected
    The setup has TWO RD Session host, 1 Session Broker, one RD Web access and one RD Gateway
    I have created 2 DNS records named Rdsfarm.domain.com for my RDS1 and RDS2 session host servers and if I connect to this
    rdsfarm.domain.com with RDP from TS clients, i am able to connect to any one of TWO rds servers without any problem
    However some part is not clear to me
    I have not added rdsfarm.domain.com any where except my RD Gateway server RAP policy
    Also I have added my RD Broker server in RAP allowed group above.
    I don't see any config where this farm name is associated with my RD Broker server
    I have tried to connect to RD broker server from client, but it didn't redirect me to RD session host servers
    If I try to connect to my RDS servers with their FQDN , it gives me error that I must connect thru farm name
    Can you please help me to understand relation between RD session host servers farm and RD broker server ?
    Also I would like to know what exactly happens in background when user start RDP session by entering RDS farm name
    Note that RDS farm name is generic DNS Host(A) record pointing to my both RD session host servers
    I wanted to know is there any command or configuration I missed out as I don't see any config where Generic RD Session Host Farm name (DNS Host(A) record) is associated with my RD Broker server ?
    Thanks
    Best Regards
    Mahesh

    Hi,
    If you are opening Remote Desktop Connection and manually connecting to the broker then it will not work properly because you have no way of specifying the target collection in the user interface.  If manually using the RD Client to connect is a requirement
    what you can do is set the default collection in the RD Connection Broker server's registry.
    To specify the default collection, please create the registry setting below in the broker's registry:
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\ClusterSettings
    DefaultTsvUrl     REG_SZ     tsv://vmresource.1.<VDI pool ID>
    To determine the correct value for DefaultTsvUrl please open RDWeb in a non-IE web browser and click on the icon for the collection you would like to be the default, then edit the downloaded rdp file with Notepad and copy the portion of the loadbalanceinfo
    setting that is similar to the above.
    An alternative would be to download the .rdp file from RD Web Access and double-click it to connect.
    As I mentioned above it is generally intended to have users connect via RD Web Access or RemoteApp and Desktop Connections feed or Remote Resources (uses the feed) so that the client will obtain the proper .rdp file from the server.
    To configure the FQDN that is published in the .rdp files you can use the cmdlet below:
    Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
    http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
    Below is a sample configuration based on what you have written:
    1. Published FQDN (using cmdlet above):  rdsfarm.domain.com  --> points to ip address of RDCB server.  When launching a RemoteApp or Full Desktop connection from RD Web Access, the prompt window will show this FQDN next to Remote computer.
    2. Gateway FQDN:  gateway.domain.com --> externally points to public ip address of your RD Gateway server.  TCP port 443 and UDP port 3391 need to be forwarded to the RDG's internal ip address.  When launching a RemoteApp or Full Desktop
    connection from RD Web Access, the prompt window will show this FQDN next to Gateway server.  This FQDN is set in Server Manager -- RDS -- Overview -- Deployment Properties -- RD Gateway tab.
    In RD Gateway Manager -- Properties of RD RAP -- Network Resources tab you should select Allow user to connect to any network resource or define a RD Gateway-managed group that has all of the FQDNs that the user will need to connect to.
    3. RD Web Access FQDN:  remote.domain.com --> internally points to the ip address of your RDWeb server, externally points to the public ip address of your RDWeb server.  This is the name you give users if they want to use RD Web, for example,
    https://remote.domain.com/rdweb
    If you want users to manually connect using Remote Desktop Client as well as use RDWeb it will be a bit confusing to them since they will need to use one FQDN when manually using the client and a different FQDN when using RDWeb.  You could fix this
    by having them only use one method or run RDWeb directly on the RDCB server, that way users would only need to know a single FQDN for both RDWeb and manual connections.
    4. You should have a wildcard certificate with subject of *.domain.com set for all RDS purposes in Deployment Properties.
    Thanks.
    -TP

  • Changes made on iPod don't appear when connected to iTunes

    Long story short, iTunes doesn't like it when I make changes through my iPod, and tries to "fix" them.
    If I delete a song or make changes to a playlist through the iPod itself, that change doesn't show up in iTunes. Deleted songs will be unplayable, but still appear. Newly created playlists may or may not appear. Deleted playlists are still there. Songs added to a playlist don't appear in the playlist, songs deleted from a playlist still appear in the playlist.
    If I make a change to my iPod through iTunes itself, it reflects that change on my iPod, but also reverts any changes I've made through the iPod (so, if I remove a song from a playlist through my iPod, then connect to iTunes and remove a song from a playlist through iTunes, the song I removed through iTunes will be removed from my iPod, but the song I removed through my iPod will reappear). It will also occasionally re-load songs I've deleted entirely, though they'll be greyed out and unplayable.
    As you may imagine, this is really annoying.
    I have all types of automatic syncing turned off, and I don't store any music in iTunes itself once it's been put on my iPod.
    I just want iTunes to show me what is on my iPod right now, and not revert back to whatever image it seems to have stored of my iPod when I try to make changes through iTunes. Does anyone have a fix for this?
    iPod touch 4 with iOS 6.1.6
    iTunes 12.0.1.26
    MacBook Pro OS X 10.8.5

    Try:
    - Reset the iOS device. Nothing will be lost      
    Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
    least ten seconds, until the Apple logo appears.
    - Unsync/delete all music and resync
    To delete all music go to Settings>General>Usage>Storage>Music>Tap edit in upper right and then tap the minus sign by All Music
    - Reset all settings                            
    Go to Settings > General > Reset and tap Reset All Settings.
    All your preferences and settings are reset. Information (such as contacts and calendars) and media (such as songs and videos) aren’t affected.
    - Restore from backup. See:                                               
    iOS: Back up and restore your iOS device with iCloud or iTunes
    - Restore to factory settings/new iOS device.                       

  • Remote desktop connections not showing in server manager 2012 for one of the session hosts

    This is a three server deployment with one server being the connection broker, gateway, licensing, etc with two session host only servers.
    rdmgr
    rd1
    rd2
    Using the server manager on the rdmgr connection broker (or any other server for that matter) yields only connections from rd2 with nothing from rd1 displaying.  
    Users can connect to rd1 without issue.
    At one point rd1 had the connection broker role installed also but high availability was not setup.  I removed the role hoping it would correct the problem but no luck.
    Any help would be appreciated.  Thanks.

    Hi,
    1. Is rd1 part of a collection?
    2. On rd1, in Computer Management, is the broker's computer account a member of the local RDS Management Servers group?
    3. If you run the below command do you get a list of sessions:
    query user /server:rd1
    4. Any errors/warnings in either the broker's or rd1's event log?
    Broker: Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-SessionBroker
    rd1: Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-SessionBroker-Client
    Both: System and other logs
    -TP

Maybe you are looking for