Hot answers tagged

9

If you don't want to change local or server side GPOs: Go to Control Panel -> Credential Manager. You will see three sections: Windows Credentials Certificate-Based Credentials Generic Credentials Remove the credentials from Windows Credentials and add it to Generic Credentials.


7

If I understood correctly you are looking for "Wake on LAN", which is supported by DELL Optiplex systems (at least in principle). Enable "Wake on LAN" in the BIOS of the target. Disable "Deep Sleep" in the BIOS of the target. On your "other" Computer (assuming it is in the same LAN) install wakeonlan. This tool can send "magic packets" to the target. Now ...


6

Sysprep isn't needed to prevent duplicate SIDs. The more I thought about it, the more I became convinced that machine SID duplication – having multiple computers with the same machine SID – doesn’t pose any problem, security or otherwise. I took my conclusion to the Windows security and deployment teams and no one could come up with a scenario where ...


6

Neither is 'Correct' per-say, but RDP-ing, is less incorrect. FTP-ing, SCP-ing, The Protocol is used in slang more frequently and if you wanted to be consistent I would stick with that. And if you consult the oracle


5

This applies to the following OS: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012and Windows VistaTry this command query session [<SessionName> | <UserName> | <SessionID>] [/server:<ServerName>] [/mode] [/flow] [/connect] [/counter] This should give output like the following; C:\>query session SESSIONNAME ...


5

Use Group Policy Preferences with Item-Level Targeting to create the shortcuts for each group of users.


3

The information of the last logged on user is stored at HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default and in the .RDP file. Check your server to be sure nothing is set there; Remote Desktop Session Host Configuration -> RDP -> Log on Settings. (a blank would be set for you, not the first option in the RDP option ('Use client side ...


3

Windows Server 2012 R2 comes with Hyper-V, it's own VMWare equivalent. Hyper-V includes App-V, Microsoft's answer to RemoteApp. For licensing, once upon a time you got 5 CALs included with the base server license. I'm not sure if they still do this, or if the number changes. Whether you need to renew your CALs annually depends on your licensing model. Large ...


3

By clicking, you turned the firewall back on and RDP traffic using TCP port 3389 is now being blocked. Since it's a VM, you'll need to (or have someone else) connect to it through the vSphere client and then allow an exception for incoming traffic on that port to allow the connection to work again. You could turn the firewall off again, but depending on ...


3

If you use the same underlying technology (eg: Win7 vs Win2008R2, Win8 vs Win2012, ecc.), and using the same settings (eg: sound off, color depth 16 bit, ecc) you should have the same performance connecting both to Windows clients and Windows Servers.


3

The answer is:https://technet.microsoft.com/en-us/library/cc754272.aspx By default, Remote Desktop Services allows users to disconnect from a remote session without logging off and ending the session. When a session is in a disconnected state, running programs are kept active even though the user is no longer actively connected. To understand ...


3

It sounds like you were playing with Restricted Groups. If so, the group isn't restricted any more, but everyone who was in that group has been kicked out. You need to create a new GPO and apply it. Then you can log in. After you're safely logged in, you can un-apply it and make sure the group membership is what you want it to be.


2

Yes the IPMI can only display via the graphics card that is integrated with the IPMI controller, on a SuperMicro this is usually a Matrox or an AST, as listed in the specs of the motherboard. This can get especially interesting if you use a newer Intel CPU with integrated video, like the E3-1275 v5. The IPMI can only display video via the AST video card, ...


2

I think i found the solution to this problem. Open this in the workstation where you want to connect, Control Panel\System and Security\System, click Advance System Settings. On the Remote tab, on the Remote Desktop group, click the button Select Users... Click Add and add the user that you want to have access. If you are using AD, make sure you can ping ...


2

You may encounter this error when connecting after importing an SSL certificate (and associated private key) into Windows Server 2012: This computer can't connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. In addition, in the Windows event logs, you see: ...


2

Affinity Groups are no longer a thing. Regions are the grouping mechanism now. Make sure your VMs and VNet are in the same Azure Region (such as East US 2, in my case). I can successfully connect to my VPN (Point-to-Site) and RDP to my IaaS VMs, without any Endpoints exposed.


2

When you are configuring your remote desktop connection, there is an option that is labelled 'local resources' from there you can pass through local drives to the target machine. You shouldn't have needed to install remote desktop from the store since the client is included by default. In the search box on the taskbar, type remote desktop and it will appear ...


2

You will get this logon type 3 when you are using NLA (Network Layer Authentication) as the authentication type since it will try and pre-authenticate you prior to giving you RDP access. You can test this by changing the security layer to RDP Security Layer. Instructions and detailed information on how to do so are found here: Configure Server ...


2

It's a result of aggressive auto-tuning of the connection which causes the delay on startup. Running the following should resolve your issue. netsh interface tcp set global autotuninglevel=highlyrestricted More details: Remote Desktop slow problem solved


2

Take a look at the output of yum group list you will find a number of options for installing various desktop groups. You can then for example use yum groupinfo Desktop ... Group: Desktop Group-Id: basic-desktop Description: A minimal desktop that can also be used as a thin client. To get more information on the relevant group. Once you ...


2

One way to accomplish this goal would be through the use of AppLocker. An excerpt from the link above: AppLocker helps administrators control how users can access and use files, such as executable files, packaged apps, scripts, Windows Installer files, and DLLs. Using AppLocker, you can: ... Create exceptions to rules. For example, you can ...


2

Use with caution (as per Microsoft): There is a registry entry you can enter so this will go away: HKEY_LOCAL_MACHINE - Software – Microsoft – Terminal Server Client Add a new DWORD called AuthenticationLevelOverride and set it's value to 0. AuthLevelOverride You can also push this out via GPO: Open Group Policy Management and create or edit a Group Policy ...


2

These will be automated scans ... Configure your firewall with a default DROP policy on incoming connections. Only allow incoming connections on ports that are in use. Restrict access to ports that are not public to specified IP addresses. Don't have your database exposed to the wider internet.


2

You should be able to connect to the 'console' session by running mstsc /admin at start>RUN If you don't have terminal services in your environment, it's likely you exceeded the maximum number of sessions (2 remote) included for management purposes, which is why you should always use the console session. If you have multiple users administering the ...


2

If you're getting an RDS licensing error then it means that you have the RDS role installed on one or more servers. You do not need the RDS role to be installed in order to connect via RDP to manage the servers. If your intention is to connect to the servers via RDP to manage them then remove the RDS role and the licensing errors will go away. As Jacob ...


2

On your Linux machine, simply issue wol <MAC> For other options, give a look at wol manpage


2

Each new connection to an RDS session is not necessarily a new logon. Users will often reconnect to an existing session. You can get close by configuring sessions to log off after a certain amount of time in a disconnected state, but this has lots of ramifications depending on what you are trying to accomplish with RDS.


2

Regardless of the fact that it usually depends on the actual resolution and various aspects like sound transmitting, 100 Mbps will be more than enough to handle the traffic for 7 RDP connections. Although the whole scheme with three eight-port switches seems to be unclear and questionable.


2

From your description, I suspect your application is listening only on localhost (127.0.0.1) and this why it is not accessible externally. You can find it out yourself by running: netstat -na | grep 14356 In that case you will need to change the applications configuration so that it listens to all or on the ip address reachable externally (0.0.0.0:14356 or ...


2

This is indicative of a poor network connection. If only some users have this problem a good next step is to identify how those users connect (wired, mobile broadband, wifi, etc.) and where they are working (at home, in an office, in public). If it is happening to all of your users check your server adapter settings and verify the server is not seeing ...



Only top voted, non community-wiki answers of a minimum length are eligible