How to fix “You’ve been logged in with a temporary profile” error.

This can sometimes be caused by an improper shutdown or Windows updates that didn’t install properly.

Click Start and type in regedit. Choose “Run as administrator” either by clicking it on the right hand side or by simple right-clicking the icon and choosing it.

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Each one of these keys represents a Windows profile. Find yours by clicking through and paying attention to the ProfileImagePath value. Look for your username.

When one becomes corrupted, Windows adds .bak to the corrupted registry key and creates a duplicate registry key that points to C:\Users\Temp.

First delete the temporary key (without .bak) and then rename the original one by removing .bak at the end.

Reboot the computer and it should be back to normal when you log back in. (I’ve attempted just signing out and signing back in but the problem persisted. I believe the reboot is necessary.)

How to enable WinRM via Group Policy

In order to remotely manage computers via Powershell, you must enable Windows Remote Management.
 
Open Group Policy management.
 
Create a new GPO.
 
Right-click your newly created GPO and click Edit…
 
First we need to allow it on each computer’s firewall. Open Computer Configuration –> Policies –> Windows Settings –> Security Settings –> Windows Firewall with Advanced Security –> Windows Firewall with Advanced Security –> Inbound Rules
 
Create a New Rule
 
Microsoft was nice enough to include it as a predefined Rule
 
I unchecked Public as I will be doing connecting locally.
 
Click Allow the connection
 
The new rule should now be listed.
 
That’s it for the firewall. Now you need to go to Computer Configuration –> Policies –> Administrative Templates –> Windows Components –> Windows Remote Management (WinRM) –> WinRM Service –> Allow remote server management through WinRM
 
Syntax:
 
Type “*” to allow messages from any IP address, or leave the field empty to listen on no IP address. You can specify one or more ranges of IP addresses.
 
Link your newly created GPO. This is going to be a computer policy so connect it to an OU of the computers you would like to enable this for.
 
It’s also necessary to make sure the WinRM service starts on startup. To do this via GPO, go to Computer Configuration –> Preferences –> Control Panel Settings –> Services
 
Right-click and click New –> Service
 
Choose Automatic (Delayed Start) as the startup type, pick WinRM as the Service name, set Start service as the Service action.
 
 
Once all of your domain computers have updated their policies and had a chance to start that system service, you should be able to remotely manage them using Powershell.

How to fix “The remote desktop session was disconnected because there are no Remote Desktop License Servers available to provide a license.” (Server 2012R2)

You must be able to access the server in another way in order to do this. Mine was a VM so I was able to get into a console session through VMware vSphere.

 
Open your Registry Editor and navigate to: HKLM/System/CurrentControlSet/Control/Terminal ServerRCM and select GracePeriod.
 
Right-click this key and back it up by choosing export and putting it in a safe place.
 
You won’t be able to delete it without taking ownership first. Right-click the key and choose Permissions…
 
 
Then go to Advanced

Change the owner to your user name.

 

For good measure, choose Replace owner on subcontainers and objects under your name and Replace all child object permission entries with inheritable permission entries from this object

Now you can delete the key. After a restart you should be able to access your server via remote desktop again.

How to shadow Remote Desktop Sessions on Windows Server 2012R2.

With Windows Server 2012 R2, Remote Desktop Services allows you to “shadow” users that are remoted into the server.
 
When shadowing, you can either view or view and control a user’s session. You can choose the option for “No Consent” allowing you to bypass user permission when connecting to their session.
 
This can be done through the command line or through the Server Manager.
 
Command Line
 
Mstsc.exe [/shadow:sessionID [/v:Servername] [/u:[Username]] [/control] [/noConsentPrompt]]
 
/shadow:ID Starts shadow with the specified sessionID.
 
/v:servername If not specified, will use the current server as the default.
 
/u:username If not specified, the currently logged on user is used.
 
/control If not specified, will only view the session.
 
/noConsentPrompt Attempts to shadow without prompting the shadowee to grant permission.
 
Below are the steps to do it through server manager.
 
Open the Server Manager and click on the icon for Remote Desktop Services. Here you should see your deployed remote environments. In my example, we have a remote app deployed to domain users.
 
One you have selected your remote environment, on the right hand side you will see CONNECTIONS listing all of the users connected to it. Right-click on one of the active users and slick Shadow.
 
 
Next it will prompt you to ask how you would like to shadow the users. Choose View or Control and whether or not to Prompt for user consent.
 

 
This is the message the user will see. It will say Remote Monitoring Request: domainuser is requesting to view/control your session remotely. Do you accept the request? prompting them to select Yes or No. If the user selects Yes, you will be able to view or view and control their session.
 

 
In the previous step, had I chosen not to Prompt for user consent, I likely would have received this error message stating The Group Policy setting is configured to require the user’s consent. Verify the configuration of the policy setting. This is by default. 
 
 
 
If you would like to be able to view or view and control a remote session without their consent, you must change the following Group Policy Setting and apply it to the preferred User Group.
 
Create a new group policy or change an existing policy and go to User Configuration –> Policies –> Administrative Templates –>  Windows Components –> Remote Desktop Services –> Remote Desktop Session Host –> Connections
 
The only available setting to change here is Set rules for remote control of Remote Desktop Services user sessions
 


Right-click the setting and choose Edit. A new window will open allow you to select Enabled and the option for how you would like to allow administrators to interact without user consent.
 
 
 
Assuming you changed the setting correctly and applied it to the correct user group, wait for a group policy refresh or force a gpupdate on the Remote Desktop server and you should now be able to do this.

How to fix RD Connection Broker, Web Access and Gateway certificates expired.

Open your Server Manager and go to Remote Desktop Services.
 
 
Click on Tasks, Edit Deployment Properties.
 

Click on Certificates.

If any of these are expired, I am going to show you how to get them up to date.
 
Now we need to get into the certificate store. If you haven’t already created an MMC for your certificates, it’s a good idea to do that now. Otherwise you can go to Run and type certlm.msc and hit enter.
 
Otherwise, start a new MMC (Start —> Type MMC) or add it to your existing one. 
 
File, Add/Remove Snap In
 

 
Highlight Certificates and click Add.
 
 
Next I chose Computer Account
 
 
Select Local Computer.
 

 
Now hit Finish and OK.
 

 
Expand Personal, select Certificates.
 

 
Right-click the certificate you would like to use, choose All Tasks, Export.
 

 
Click Next
 

 
Choose Yes, export the private key. Click Next.
 

 
You can leave this as is. Click Next.
 
 
This next step is up to you. You can protect it with your own unique password or choose Group or user names and assuming you’re logged in, it should populate your username below.
 
 
By default it wants to save your newly created certificate to System32. I elected to click Browse, created a new folder on the C: drive and put my newly created PFX file in there.
 
 
Once that’s all done. You can now go back to the Deployment Properties window that we had open earlier. Highlight the Role Service with the expired status and click Select existing certificate…
 
 
Click Choose a different certificate and Browse for the one we just exported earlier.
 
 
Select Allow the certificate to be added to the Trusted Root Certificate Authorities certificate store on the destination computers and click OK
 
 
Now it should say Ready to apply and click Apply. These all have to be done one at a time. If you did everything correctly, the Status should change to OK.
 
 
Click OK and you’re done.

How to set Remote Desktop Licensing Mode (Server 2012R2)

Open your Server Manager.
Click Remote Desktop Services on the left hand side.
Select the Overview branch.
In Deployment Overview area, select Edit Deployment Properties from the Tasks menu.
Select RD Licensing.
Choose the licensing mode and enter the name of the license server, click Add and then click OK.

How to redirect Rdweb page from IIS 8 root site.

After you have successfully deployed a Remote Desktop Web Access server, users have to type sub.domain.com/rdweb/pages/ to reach it.

 
To make it easier, you can redirect sub.domain.com to sub.domain.com/rdweb/pages

Open Internet Information Services (IIS) Manager.

Choose your site. I only have one so mine is the Default Site.

Double click on HTTP Redirect.

Check the box Redirect requests to this destination.
 
Type /RDWeb/Pages as redirect destination.
 
Uncheck the box for Redirect all requests to exact destination (instead of relative to destination).
 
Check the box for Only redirect requests to content in this directory (not subdirectories).
 
Select Status code as Found (302).
 
 
Try typing https://sub.domain.com. It should now redirect you to the RDWeb page.

Printer settings could not be saved. This operation is not supported. Server 2012 R2

How to fix “Printer settings could not be saved. This operation is not supported.” (Server 2012R2)

So here’s a really annoying one and it has to do with printers. Of course right? It always printers or DNS. ALWAYS.

 
Anyway I wanted to change the driver on one of my deployed printers when I ran into this message:
 
“Printer settings could not be saved. This operation is not supported.”
 
After some digging around, I was able to find the culprit. It’s because there is little box that’s ticked called “Share This Printer” under the Sharing tab.
 
 
Untick that box, click apply, install your new driver, then go back and tick that box again.
 
 
Also make sure you tick the box to List in the directory again if you had that on too because it gets turned off by default when you un-share it.

How to fix clients not reporting to WSUS target groups.

So I came across this this morning which was a simple fix but easy to miss. I noticed that my computers still weren’t going into the target groups that I assigned via Group Policy. Here is how to fix it.

 
 
Click Options on the left-hand side.
 
 
Click Computers.
 
 
Select Use Group Policy or registry settings on computers and click OK.
 
 
Now just wait a bit and the next time your computers send their status to the WSUS server, they should begin to fall into the groups that they belong in.
 

How to configure clients to pull updates from a WSUS server through Group Policy Management

 
Open Group Policy Management (above).
 
Drill down to the Organizational Unit containing the computers you would like to configure this for. This is a Computer Policy so no need to apply this to any OU containing Users. Right-click and choose Create a GPO in this domain, and Link it here…
 
 
Name it.
 
 
Click OK. Drill down to Computer Configuration –> Policies –> Administrative Templates –> Windows Components –> Windows Update.
 
 
Here are some of my settings. Notice the setting called Enable client side targeting. This is where you name the target group that these computers are listed under in the WSUS console.
 
 
The most important one is the one that tells your computers where your WSUS update server is.
 
Scroll down to find Specify intranet Microsoft update service location. Enter your WSUS server’s Fully Qualified Domain Name (FQDN) followed by the port number. I set them both the same. The default port is 8530.
 
ex. server.ad.mycompany.com:8530
 
 
That’s it. You should see the Group Policy Object (GPO) that you just created in the Organizational Unit. Assuming you’ve properly organized your computers into this group, once your clients do a Group Policy Update, they should begin pulling updates from the WSUS server you set up. You can also force a Group Policy update on the clients by opening a command prompt and typing ‘gpupdate’.
 
 

Scroll to top