We had a issue with a new Windows 8.1 install, when the user login to the RemoteApp Web Access Portal, and opened a Remoteapp, it´s just stuck on “Preparing Windows”, the same thing happens if i used the RemoteApp and Desktop Connections from the control panel.
To fix it i added the RD Web Access url to trusted sites in Internet Explorer.
example: *rds.company.com
From Server Manager it´s not possible to publish an application from a Network shared folder, But from Powershell you can do it, here is how:
New-RDRemoteApp -Alias "App Name" -CollectionName "Collection" -DisplayName "APP DisplayName" -FilePath "\\server01\apps\app.exe" -ConnectionBroker connectionbroker.domain.local
If you Windows is stuck in a rebooting loop “rebooting into Windows recovery / repair mode”
put in a Windows disc and start a commandline and run this command to disabled it:
bcdedit /set {current} recoveryenabled No
In Windows 8.1 Microsoft made a bigger change related to desktop performance.
By default Users logon scripts is 5 minutes delayed.
To disabled or reduce the delay between user logon and when the scripts run, find this policy in Group policy Editor
“Computer Configuration\Policies\Administrative Templates\System\Group Policy\Configure Logon Script Delay”
I installed Adobe Reader XI on our Windows Server 2012 R2 RDS servers, and we start to get this error when we started Adobe Reader.
After some time on Google i found out that disabling Adobe Reader XI sandbox protection mode fixed the error.
go to the registry and find this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\11.0\FeatureLockDown
Create a new REG_DWORD
Value Name
bProtectedMode
Value Data
0
To easy change Automatic Start Action on all runnings VM´s on your Hyper-V server run this command:
Get-VM | Where { $_.State –eq ‘Running’ } | Set-VM -AutomaticStartAction StartIfRunning
To validate it run this command:
Get-VM | Where { $_.State –eq ‘Running’ } | ft Name, AutomaticStartAction -AutoSize
Microsoft had released an update for Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012 KMS Hosts to support WIndows 8.1 and Windows Server 2012 R2
http://support.microsoft.com/kb/2885698/en-us
Install the update and reboot, then add the new Windows Server 2012 R2 or Windows 8.1 KMS Host key
We have had performance issues for a few weeks at night, all our Hyper-V Servers where performing like CRAP every night around 3 AM and for about 45 minutes.
After a long night of investigation with my colleague, we found out that Windows 2012 is running a maintenance job around 03:00 each day.
When we stopped it all began to run as normal. This caused overloading of the SAN SP and gave high disk queue on all servers attached to the SAN.
But, after we disabled the Scheduled Task “Regular Maintenance“, it got enabled Again after some hours.
To avoy this disable “Maintenance Configurator“, but this can´t be done from GUI
To disable Maintenance Configurator run this command on a server with PsExec Link :
psexec \\SERVERNAME -s schtasks /change /tn "\Microsoft\Windows\TaskScheduler\Maintenance Configurator" /DISABLE
This update lets servers that are running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012
Recently i got this error when trying to enable Cluster Aware Updating in Server 2012, i got this error:
“Unable to create the CAU clustered role because a Network Name resource could not be created. This can occur if a computer account (virtual computer object) for the role could not be created in the domain. Check the event log for more information. If the cluster name account does not have permissions to create the object, you can pre-stage a computer account in Active Directory. Then, use the Add-CauClusterRole Windows PowerShell cmdlet with the VirtualComputerObjectName parameter to create the CAU clustered role. For more information about pre-staging computer accounts, see http://go.microsoft.com/fwlink/p/?LinkId=237624.”
to fix this open Active Directory Users and Computers, go to view and select Advanced Features. Navigate to the OU where your Cluster object will be created and right-click on the OU and choose properties., go to the Security tab. Add your Hyper-V cluster computer object, then choose Advanced. From there select your Hyper-V cluster object and choose Edit. Navigate down to “Create Computer objects” and choose check the check box.
Click Apply and Ok, then try enabling CAU again!
Note: By default the new CAU object will be created where the cluster object is.