Microsoft Stuff

Windows Server 2012R2 cannot find License terms

admin@bubbakraut.com (Sven Jambor) — Fri, 19 Sep 2014 11:28:09 +0200

Installing Windows Server 2012R2 as a virtual machine on a Windows Server 20112 Hyper-V host is easy. Mostly.

There IS a small caveat that had me pulling my hair out, though: Just quickly throwing a small vm into operation - accepting all the defaults - would result in a pesky error regarding the licensing terms. The message said "Windows cannot find the Microsoft Software License Terms. Make sure the installation source is valid and restart the installation."

Do I trust myself? Heck, yes!

admin@bubbakraut.com (Sven Jambor) — Mon, 04 Jul 2011 12:50:39 +0200

Here you are, all proud that you finished your first Powershell script. Cool! Congrats. PAt yourself on the back!

Now try running it. Most likely you're getting a little pesky prompt telling you to run the script only if if you trust the publisher of the script, blah, blah blah. Great stuff - if you downloaded the thing from the Big Bad Internet - but VERY annoying if you want to run the script automatically (e.g. as a login script or the like). Of course I trust the publisher! I'm not THAT paranoid! So here's how to get around the prompt (drum roll, please): Use the ExecutionPolicy switch!

PowerShell -ExecutionPolicy Bypass -File

Moving the User Profile location

admin@bubbakraut.com (Sven Jambor) — Tue, 31 May 2011 14:34:47 +0200

We needed to move the location of where the user profiles on a Windows 2008 R2 Server are stored from C: to D: . This turned out to be a bit more work than anticipated - hence this article.

WSUS download stuck

admin@bubbakraut.com (Sven Jambor) — Fri, 20 May 2011 14:09:08 +0200

Okay, WSUS is all set up nicely & updates have been approved. They start to download - and suddenly stop. No progress is to be seen in the number of packages downloaded and the amount of data. Now what?

Zones assignment fails in IE with ESC

admin@bubbakraut.com (Sven Jambor) — Tue, 10 May 2011 13:51:56 +0200

Okay, this pretty much bugged me out: We had IE8 running on a Windows Server 2008 R2 RDS server (yes, Terminal Server for all you OldFolks). We had certain sites assigned to specific Internet Explorer zones (some backing sites to "Trusted", some internal stuff to "Intranet", etc). Everything worked hanky danky when logged on locally - but users connecting with REmote Desktop Services do not get the site-to-zone assignment lists applied.

Form scripting on RDS

admin@bubbakraut.com (Sven Jambor) — Tue, 10 May 2011 08:34:16 +0200

Try one thing: install Microsoft Office (pretty much any version) on a Terminal Server (sorry, it's Remote Desktop Session Host, or RDS Host, since we're on Server 2008 R2). Then try to use some advanced Outlook forms - like what we do with IronMountain (formerly Mimosa) NearPoint. Chances are you'll see a message telling you to bugger off - because Form scripting is not installed.

Show only certain Control Panel items

admin@bubbakraut.com (Sven Jambor) — Wed, 04 May 2011 13:45:43 +0200

Somtime you want to protect computer users against themselves. Especially in Remote Desktop Session (ie.e. Terminal Server) environments that would be an excellent idea.

One of the things you might want to do is to restrict the control panel items your users can access. In the past you did that by specifying which .cpl applets were permitted. Not so any more - of course

Call me Über-being

admin@bubbakraut.com (Sven Jambor) — Wed, 04 May 2011 12:59:24 +0200

Okay, I was browsing around looking for the control panel applet names in Windows Server 2008 (or Windows 7, or Windows Server 2008R2, for that matter) to include in a new policy. Not that you ned to know what I was doing, but just throwing it out there.

Anyway, over on petri.co.il I came across a cool thing: GOD MODE.

SSO for RemoteApps

admin@bubbakraut.com (Sven Jambor) — Mon, 11 Apr 2011 09:43:27 +0200

Okay, call me slow in the uptake. But what's the point of looking stuff up that you got no use for? None. So, until recently I didn't need to find out how to enable Single Sign on for users of a Terminal Server who want to use a Remote App on another machine. Luckily. The MS team already had a great blog post on enabling SSO for REmote Apps in Remote Desktop Serices.

Find it here: http://blogs.msdn.com/b/rds/archive/2007/04/19/how-to-enable-single-sign-on-for-my-terminal-server-connections.aspx