Quantcast
Viewing all 27656 articles
Browse latest View live

Shadow session - black screen

Hello,

I encounter following problem - when admin tries to connect/control another session on the terminal server (from the server) - windows opens but has only black screen.

Sometimes 2-3 reconnects helps, but usually it does not.

Any ideas?

Thank you!


Multipoint 21012 "Take control" from Dshboard failed

GoodDay

I have installed WindowsMultipoint2012Premiumand I use Direct-Video-Conetedstation.
When I want to use Dashboard, it worksfine, but when I want to"TakeControl"- it appears the following error message;

"The Take Control Failed action.Multipoint can not connect tothe session "

Same if I use the"Project":error messageis:

"Project failed.Unable to connect tosession"


Ido not usevirtual machine.I do not useWMP2012virtual.
It is installedas the operating systemonan Inteli7with16GBRAM.ConnectionusingNVIDIAQuadro440 (and/or Nvidia Quadro nvs 295)+USB HUB+monitorandthe second Config. (connection)is aZeroClientHPT 200.
I reinstalledWMP2012several times.Tackecontrolsometimesworkedand sometimes not.I do not knowwhy.

Pleasehelp me,
What should I do?

Thanks
Patrasescu.marinica@yahoo.ro

Publisher of this remote connection can't be identified

I have an environment that is exploding into about 3000+ virtual Windows 7 PCs across 14 Windows 2008R2 and Windows 2012R2 clusters and users sitting at Wyse thin clients running Win7e.  We were using the connection broker in Windows 2008R2 but that was a pain and when we started upgrading to Windows 2012R2 server to host the virtual PCs the broker changed and in general Microsoft's brokers didn't work too well especially if a cluster member crashed (Win2008R2) and all the VMs abandoned ship, the broker did not know how was hosting the VMs now and you'd get errors trying to connect.....

We designed our own broker, a simple webpage that asks the user their username, looks it up in the tsMSPrimaryDesktop field like Windows 2008R2's connection broker used to.  This is also the field under the Personal Virtual Desktop tab in AD Users and Computers.  Since we just use the Hostname of the virtual PC it works across all the clusters no matter the version.  The webpage does some other stuff like ping your virtual to make sure it's online, see if the user account is locked, etc but in general it then simply generates an .RDP file (with our preset settings), sticks the PC name in the "full address" line and also drops in the username supplied previously to "username" line (why ask the user twice).

Problem is the "Publisher of this remote connection can't be identified" popup.  This entire environment is a closed network, NO internet access whatsoever.  

I've seen articles talking about using certificats to sign the RDP files and such but I have ONE .RDP that is "generated" on the fly called GOTOMYPC.RDP.  This .RDP actually contains simple ASP code and the IIS server is told to run *.RDP files through the ASP compiler so when the users thin client sees it it knows the default app for an .RDP file is MSTSC.

Can't I just set a setting on the thin clients in the registry that we don't care don't check for certificates or whatever?  Similarly the way you can tell IE "Don't do certificate revocation checks" etc...  Making 3000 RDP files that are signed does not seem like a logical solution.


-------------------- Joe O'Bremski

When attempting to Shadow on 2012 R2 RDS we get an Unspecified error


We have built a Windows server 2012 R2 RDS server, and setup the whole deployment on one server, Gateway, Broker, licensing, session host, and collection.

But when we go to shadow the user using Server manager or command line mstsc /shadow:n when get this very helpful error:   Unspecified error in a Window called Shadow Error

I have tested Shadowing on another networks server with a similar setup and it works fine, only difference is the Active directory server are 2008 vs this one that doesn't work being 2003.

I have also tested using local accounts and still get the same error, and there is not a lot on the web regarding this error and RDS shadowing


PDF Preview handler error with outlook 2013 on RDS 2012R2

Anyone had any issues with outlook x64 2013 office and "PDF Preview handler", we are running adobe 11 with server 2012 R2. CHecked all the recommended reg settings are correct:

"Change the AppID value to {534A1E02-D58F-44f0-B58B-36CBED287C7C}"

However still prompted with "this file cannot be previewed because of an error with the following previewer: PDF Preview handler"

Also causes a popup box to say an internal error has occurred.

Loads fine when you double click the attachement.

How to specify Host Server for Replicated Virtual Desktops within RDVH Collection

My question about how to specify Host Server for Replicated Virtual Desktops within Collection.
I know there is a aswered thread on this, but that solution (wait a week) didn't work for me.

So i have 2 servers, RDS01 and RDS02 with both 15 Hyper-V VM's and replicating to eachother. That part works fine.
Now I wanted to make it easy for my users I build a Connection Broker: RDCB

All went fine in that setup, but when I want to add the existing VM's from RDS01 and RDS02 to the collection it just radomly adds running ones and replicated ones.

So both RDS01 and RDS02 have 15 VM's running and 15 replica's in stopped state, but when I look in my collection, it says RDS01 has 23 and RDS02 has 7 VM's. When I add them all, I see he wants to add a lot of stopped states replica's from RDS01 instead of the running ones from RDS02.

How can I specify which one he should use? Or need I disable replication first, setup the whole RDCB collection thing, and then turn replication back on? Or does Hyper-V replication not work at all when used in a collection?

I hope someone can help out here. I'm googling and trying for 1,5 week now, but i can;t get it right.

Thanks in advance.

outlook 2010 hangs in exchange 2013 (both in Hyper-V)

We have a Hyper-V AD/DC Server 2012, a Hyper-V Exchange Server 2013 and a Hyper-V RDS-Server 2012 running on a HP Proliant Server. Everything worked fine in the beginning (half a year ago), but since recently Outlook 2010 which is installed on the RDS-Server hangs while trying to acces the emails. There are 4 users working on the RDS-Server with outlook mailboxes from 6Gb up to 17Gb (that has the most problems). After every problem we have to repair Office 2010 and then it works again for a few days. The RDS-Server in Hyper-V has 12Gb memory. The other users that work locally in this domein do not have this problem, only the ones with Remote Desktop. I tried almost everything but cannot figure it out. Hopefully someone has a sollution for me? Thanx in advance for any steps in the right direction!

VDI - RemoteApp does not start in "Virtual machine-based desktop deployment" environment

Hello dear community,

I would like to familiarize myself to the subject of desktop virtualization and have built up a test environment for this purpose. Most went smoothly, but now I'm trying for days to figure out, why the deployed RemoteApp programs in my test environment not start. Unfortunately posts here and in other blogs were not helpful. I hope you can point me to the right direction. :)

My environment

Server 1
Windows Server 2012 R2 Std with the roles
    AD DS,
    DNS,
    DHCP

Server 2
Windows Server 2012 R2 Std with the roles
    Hyper-V,
    Remote Desktop Services (Connection Broker, Virtualization Host, Web Access),
    IIS

VMs
Windows 8.1

RD Client 1
Laptop with Windows 7 and Internet Explorer 9, Firefox 28, RemoteApp and Desktop Connections

RD client 2
iPad with Microsoft Remote Desktop App

Setting up the environment

The installation of the environment I made as mentioned ​​in the following blog post. http://blog.itvce.com/?p=1569 But with only two physical servers.

What does work?

Prepared with SysPrep and "cloned" Windows 8.1 VMs created in the collections of virtual desktops are accessible via WebAccess (RDWeb) using IE, FF, Windows Start menu and also from the iPad as a complete desktop for authorized users/groups. The VMs wake up in Hyper- V from the saved state and roll back to it after the user logs off. So far so good.

What does not work?

Now to what does not work. One collection of virtual desktops I have reserved for the publication of RemoteApp programs. So this new collection - like the above - was created. The VMs were built and successfully registered in AD. Then I used "publish RemoteApp Programs" wizard in the collection. The available programs were successfully read from the VM. WordPad, Calc and Paint I used for the test. The programs/apps will then appear in RDWeb.

In RDWeb I now click on the Calculator, the warning described in many blogs appears that resources are passed through and then that the certificate could not be verified. Although I have already added the certificate to the trusted root CA in the user and the computer area, I acknowledge that I would like to connect despite the certificate error with "Yes".

After about 20 seconds the "Connect to ..." window disappears and that it was. In Hyper-V Manager the corresponding VM does not move even if it's running. If the VM was not running and in saved state, it is at least started. But the Calculator will still not start.

Can anyone give me a proper hint what to do, which Bing, Google and Technet did not have?

Thank you in advance!
Kay

PS: Since I am from Germany, I have asked the question first in the German forum. Unfortunately, without success.

RemoteApp and Desktop Connections Error 0x800401F0 when updating RemoteApp connections from RDS webfeed

Environment:

Windows Server 2012 R2 with RDS roles installed.

Windows 8 clients

Issue:

The RDS Webfeed doesn't updated automatically. Instead, I get an error:

"An error occurred while updating this connection. Error code: 0x800401f0, 0x0"

I can perform a manual update in the control panel, but the users who will be using this on a regular basis are blocked from the control panel by a GPO.  Also, I don't want end users to have to perform this update manually anyway.

I've included a screenshot of the issue for reference. Image may be NSFW.
Clik here to view.


DuRand Bryant

userhomes created with .domain appended

HI, 

I have 30-40 standard win 7 Desktops users for which we have redirected Home Folders  to a network share \\servername\userhomes$. This is done via Group Policy. The desktop users don't have roaming profiles, we just re-dircect the the Userhomes.

I am just rolling out a Terminal Server 2008 R2 . I am trying to re-direct the user homes to the same location so the users get the access to the same "my documents folder" whether they are logging in from thier local desktops or to the Terminal server. 

When  a user first logins to the TS server, for some reason,  a brand new Userhome is created with the format:  username.domain even though an existing folder with the correct username already exists.

If I create a new User and log into the terminal server first a new userhome is created for the user with the .domain added. 

If I create a new user and log into a desktop first then a new userhome is created with  just the username and without the domain. 

Why is the .domain added to the username when this is not specified? 

How can I achieve my goal of just having one user home directory which is used whether logging to terminal server or to the a local desktop 

Look forward to your help with this. Many thanks Richard

Check RDP connection version

We think we have completed all of the client and server prerequisites to enable RDP 8.1. But how do you check whether a connection is actually using RDP 8.1?

Looking at the version of the Remote Desktop Client will not help because this only tells you what the client is capable of, not what the connection is actually using.

We cannot use the new 'strength indicator bar' because the clients are connecting to published applications externally via RD Gateway, and this is not shown.

I'm assuming there's a command or console we can run or a log we can look at?

Suggestions welcome! Thanks.

Incrorect User Name and Password Error

My Scenario

1. 4 x VMs (1 x Windows Server 2008R2 Domain Controller, 1 x Windows Server 2008R2 client & 2 x Windows Server 2003 clients)

2. 3 x client machine are domain joined.

3. server 2003 machines are accessible via rdp and no issue.

4. When 2008R2 machine accessed from 2008R2 management machine, gives user name / password error continuously, when same machine accessed from 2003 client, logon is successful.

5. Local admin logon to machine is sucsessful and all domain related tasks are performed with no issue, accept domain user credentials at every prompt.

6. DNS working fine. ping to domain controller and vice versa fine.

what is the reason of incorrect user name and password while i am entering correct one.

Thanks for reply

Mapped Drives show a red cross in Terminal Server 2012

Have recently built a new Windows 2012 R2  sever on the network and installed Remote Desktop Services. When users connect to the 2012 Terminal Server, their mapped drives show a red cross. They are still able to access the network drive though and when they do, the red cross does not disappear.

Have spent countless hours researching this problem on the internet but still haven't found a fix. Have tried the following

- Instead of mapping drives using GPO, have used a logon .VBS script
- Deleted TS user profile
- ran command net config server /autodisconnect:-1
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service\lanmanworkstation\parameters  Value: KeepConn
  Data type : REG_DWORD
  Value  : 65535
- enabled the GPO -
Always wait for the network at computer startup and logon

Read the following articles. Couldn't do much as these articles don't apply to Windows 2012
- http://support.microsoft.com/kb/938062
- http://support.microsoft.com/kb/2551503/

- http://support.microsoft.com/kb/2775511/en-us

Observations

- The first user that connects to the Terminal Server session gets the drives mapped fine however subsequent users get the red cross in their drive mappings

Am at my wits end! Have even tried rebuilding the server from scratch but the problem still exists. I don't have any problems on another server Windows 2003 TS with the same GPO being applied to the users.

Error Publishing a Remote App Hosted on a Windows 8 Desktop

I am attempting to publish a Remote App from a Windows 8 pooled VM and I'm receiving the following error message:

Image may be NSFW.
Clik here to view.

I have tried to publish the applications from both Windows 8 and 8.1 Enterprise x64 Editions and both give the same error. I have addressed both of the conditions listed in the error message. My user account is an enterprise admin and a domain admin so I should have rights, but just to be safe I added my account directly to the administrators group on the VM with no success. I am also able to ping the workstation and RDP successfully so it is clearly available on the network. 

Is there a magic step that I'm missing or that isn't documented or can someone point me to a good how-to?

I appreciate the help!

Group Policy to Allow Non-Administrative Users to View All User Processes in Task Manager

Hi All:

Trying to get users with just Remote Services right (can remote in, no administrative permissions what-so-ever, to have the ability to view all processes by all users on the server.

I would like to do through group policy, however I cannot seem to find a policy doing just this. Any ideas?

2008 R2 Forest btw.


Administrator allowed to establish Remote Desktop sessions but other administrators are not allowed

Hi,

I have recently installed a Windows Server 2012 R2 with Updates for Data Center onto one of my servers. I then enabled remote desktops via the Local Server page from Server Manager. I am able to connect to the server using the server's Administrator account. However, when I try to establish a remote desktop connection using another account that is a member of the Administrators group, the message "The credentials that were used to connect to <server> did not work. Please enter new credentials".

Please advise.

Thanks.

Br,
Ethan



W2K8R2 RemoteApp on W7x64SP1 Clients - with only specific drive reconnected

Due to article http://fragged.info/tag/drivestoredirect/ there is no possibility to reconnect only one specific drive of the Client starting the RemoteApp.

The only possibility is to show "all" drives or "no" drives from the Client.
In a remote Desktop session it can be done using "drivestoredirect:s:D:;" for example in .rdp configuration file.
But this does not work in RemoteApp.

Are there any news or solutions regarding this Problem?
How could redirection - else - work with only one specific drive in Remote App?

Paperwork for the original TS licenses

Microsoft Azure RemoteApp API

Is there or will Microsoft announce some kind of the API for the Microsoft Azure RemoteApp? 

-- Innovative monitoring solution for Remote Desktop Services/Terminal Services http://www.terminalserviceslog.com/

Access local drives for some users

Hi

I have small issue with RDS 2012R2, I can make access of local drives for all users, but if i make one GPO for some users to allow access and another GPO to prohibit for rest of users then I get problems.

I cannot make it work for 2 GPO´s, only one GPO works.

Is it limitation in GPO and Windows that you cannot have 2 same computers settings in 2 diffrent GPO that applies on same server?

Regards,

Dalibor Sinik

Viewing all 27656 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>