RDS 2012: Publish apps installed on a network share

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
No tips yet.
Be the first to tip!

Like this post? Tip me with bitcoin!

172uZsyKZ92rwaLPpuoNzivawmde7C4QTm

If you enjoyed reading this post, please consider tipping me using Bitcoin. Each post gets its own unique Bitcoin address so by tipping you're not only making my continued efforts possible but telling me what you liked.

VN:F [1.9.22_1171]
Rating: 6.0/6 (1 vote cast)

Fix: Windows Stuck in a “Preparing Automatic Repair” loop

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

 

No tips yet.
Be the first to tip!

Like this post? Tip me with bitcoin!

1ad5ctJe6JyMpMgq43rhHhib2YgP86NKJ

If you enjoyed reading this post, please consider tipping me using Bitcoin. Each post gets its own unique Bitcoin address so by tipping you're not only making my continued efforts possible but telling me what you liked.

VN:F [1.9.22_1171]
Rating: 3.4/6 (16 votes cast)

Adobe Reader XI – An internal error occurred

Adobe Reader An Internal Error Occurred

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

2 tips so far
0.00713607 BTC
(avg tip 0.00357 BTC)

Like this post? Tip me with bitcoin!

1Ma2gb38cDjjuR3n1DzivVoLqjm5XeaiJ2

If you enjoyed reading this post, please consider tipping me using Bitcoin. Each post gets its own unique Bitcoin address so by tipping you're not only making my continued efforts possible but telling me what you liked.

VN:F [1.9.22_1171]
Rating: 5.8/6 (32 votes cast)

Server 2012 “Automatic Maintenance” Killed our SAN

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.

The Automatic Maintenance window in the Action Center
The Automatic Maintenance window in the Action Center

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
Maintenance is now disabled.
Maintenance is now disabled.
No tips yet.
Be the first to tip!

Like this post? Tip me with bitcoin!

13o91y2bVQgzt78Sx1J3yQwYUET74WGGqz

If you enjoyed reading this post, please consider tipping me using Bitcoin. Each post gets its own unique Bitcoin address so by tipping you're not only making my continued efforts possible but telling me what you liked.

VN:F [1.9.22_1171]
Rating: 5.9/6 (7 votes cast)

WSUS 3.0 SP2 Hotfix to provide updates to Windows 8 and Windows Server 2012

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

http://support.microsoft.com/kb/2734608

No tips yet.
Be the first to tip!

Like this post? Tip me with bitcoin!

11mMq4HVs3gquSdJHZ6b38y9rLD1azMHP

If you enjoyed reading this post, please consider tipping me using Bitcoin. Each post gets its own unique Bitcoin address so by tipping you're not only making my continued efforts possible but telling me what you liked.

VN:F [1.9.22_1171]
Rating: 0.0/6 (0 votes cast)

Unable to create the CAU clustered role because a Network Name resource could not be created

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.”

Unable to create the CAU clustered role because a Network Name resource could not be created
Unable to create the CAU clustered role because a Network Name resource could not be created

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.

No tips yet.
Be the first to tip!

Like this post? Tip me with bitcoin!

1C8CfJd3vi9LCdqTYWm5bJnnfQmLVXSzH

If you enjoyed reading this post, please consider tipping me using Bitcoin. Each post gets its own unique Bitcoin address so by tipping you're not only making my continued efforts possible but telling me what you liked.

VN:F [1.9.22_1171]
Rating: 6.0/6 (7 votes cast)

KMS Update to Support Office 2013

Microsoft had released an update for Windows 7 and Windows Server 2008 R2 KMS Hosts to support Office 2013 KMS Hosts

Get it here:
http://www.microsoft.com/en-us/download/details.aspx?id=35584

No tips yet.
Be the first to tip!

Like this post? Tip me with bitcoin!

1G8EyndSyzEpdXKN8GCi7kSTLguhvsBW9V

If you enjoyed reading this post, please consider tipping me using Bitcoin. Each post gets its own unique Bitcoin address so by tipping you're not only making my continued efforts possible but telling me what you liked.

VN:F [1.9.22_1171]
Rating: 6.0/6 (1 vote cast)

KMS Update to Support Windows 8 / Windows Server 2012

Microsoft had released an update for Windows 7 and Windows Server 2008 R2 KMS Hosts to support WIndows 8 and Windows Server 2012

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

Installation instructions

If you have a KMS host that is running Windows Server 2008 R2 SP1 or Windows 7 SP1, follow these steps to perform an upgrade:

  1. Install this update (KB2691586).
  2. Restart the computer when you are prompted.
  3. To install a new KMS host key for Windows 8 activation or for Windows Server 2012 activation, run the following command:
    cscript %windir%\system32\slmgr.vbs /ipk <KMS host key>

Note In this command, replace <KMS host key> with the new KMS host key for Windows 8 activation or for Windows Server 2012 activation.
Important Every KMS host key is associated with a group of Windows editions. Additionally, a KMS host key that is associated with Windows client operating systems cannot be installed on Windows server operating systems, and vice-versa. This is true for all Windows operating systems except for Windows Server 2003. If you install a KMS host key on a Windows operating system that is not associated with that host key, you receive the following error message:
0xc004f015: The Software Licensing Service reported that the license is not installed. SL_E_PRODUCT_SKU_NOT_INSTALLED

For example, you receive this error message if you try to install a KMS host key for Windows 7 on a computer that is running Windows Server 2008 R2.
For more information about KMS host keys and about associated groups of Windows editions, see Table 5 in the “Determine Product Key Needs” section of the Volume Activation Planning Guide
(http://technet.microsoft.com/en-us/library/dd878528.aspx#E3IAC)

Activate the new KMS host key on the host computer, run the following command:
cscript %windir%\system32\slmgr.vbs /ato

No tips yet.
Be the first to tip!

Like this post? Tip me with bitcoin!

1KFFYS8nReDoV46FSe9VwWXUj6nFcLZmgb

If you enjoyed reading this post, please consider tipping me using Bitcoin. Each post gets its own unique Bitcoin address so by tipping you're not only making my continued efforts possible but telling me what you liked.

VN:F [1.9.22_1171]
Rating: 3.5/6 (2 votes cast)