sepago Spezialisten bloggen über Citrix und Microsoft

PowerShell provides several Location-cmdlets for the work with directory paths. This post will show you a useful task for these commands. But this is only one cool thing you can do with the cmdlets and it’s meant to encourage you to experiment on your own.

Get-Location

When we open a PowerShell console, it will show us the actual working directory. If we want to identify this directory out of a script, we can do that with Get-Location.

Execution of a ConfigMgr task sequence from Powershell

This little script or function I wrote because I saw a question on the german TechNet forums about it.

An user asked if it was possible to execute a Task Sequence from a script (Powershell in this case). There are some VBS around, but as I’m not too fluent in VBS and I like writing Powershell I thought, why not?!

I did come across some customers running Task Sequence after Task Sequence.

Here is another short script you can use on your way to automate every task in your ConfigMgr environment.

Syncing the SUP in ConfigMgr 2012

Synchronizing the Software Update Point in a ConfigMgr environment can happen in two ways – automatically or manually.

This can be configured in your site component’s configuration:

In there you can configure the SUP to synchronize on a schedule or not. If you don’t use a schedule,

Some of you might have already read on Twitter that I’m currently doing a little ‚experiment‘.
About a month ago I got me a Surface Pro and said to myself, „Now that you got it, you have to use it!“ and started to think about how to do that. I came to the conclusion that all the stuff I do on my laptop (Mail, browsing, Word, Powerpoint, Excel) can easily be transfered to the Surface,

Did you know that there are subtle differences how Wi-Fi works depending on the geographical region you are in? For example, you may have issues operating a US device in Europe. The device will not be able to see or connect to some wireless networks.

US Surface Pro

I was affected by this issue and it took me three weeks to nail this issue with the help of my colleague Marcel Meurer.

In a recent deployment of Remote Desktop Services with Windows Server 2012, I experienced a second prompt for credentials. It occurred after successfully authenticating with Remote Desktop WebAccess  and launching a RemoteApp from the browser. This blog explains why the second prompt is shown and how to get rid of it.

What the user is experiencing

Launching a RemoteApp from WebAccess is usually a very simple thing to do. After logging on (see first screenshot below),

In my lab environment I tried to install and use Citrix WebInterface 5.4 on Windows Server 2012. This blog will guide you through the installation and configuration process.

Prepare your Windows Server 2012

Install the following roles and features:

• .NET Framework 3.5 Features (you need access to the Windows installation source – because of the Feature on Demand setup option)
• Web Server (IIS) with sub-components
  • Application Development
    • ASP
    • ASP.NET 3.5
• Management Tools with sub-components
  • IIS 6 Management Compatibility
  • IIS 6 Metabase Compatibility

With the release of Windows Server 2012, I wanted to upgrade my test and demo environment as quickly as possible. As with many hosting offerings, I do not have physical access to my dedicated server but do get two hours of remote console access for free. Therefore, I needed a way to deploy Windows Server 2012. This article documents how I successfully installed Windows Server 2012 on the second hard disk from a running Windows Server 2008 R2.

In a centralized environment such as a XenApp farm, users share resources with one another. A thoroughly designed platform will be able to handle all prospected users as well as provide contingencies for failures and maintenance tasks. When sizing a XenApp farm, resources as well as licenses need to be calculated for the concurrently connected users (CCU) which may well be only a small fraction of the total number of users. From an architectural point of view,

Windows Recovery Environment (RE) is based on the Windows Preinstallation Environment (PE) and can be extended to be a minimalistic system to recover a somehow broken systen. Windows RE is configured in the boot configuration data to be the failover system for the primary boot entry. If the boot loader fails on the default entry, it will automatically try to boot into the recovery environment.

Windows RE offers the following features:

•  System Repair attempts to correct typical issues rendering the system unbootable,