Skip to main content

Windows 8 To-GO

By

I spent last night at the Microsoft officer here in Indianapolis with the Indiana Windows Users Group.  We had a demonstration on Windows 8 To Go and a lot of pizza.

This new feature of Windows definitely opened my mind to some new potential work scenarios.  Since it is bootable on any hardware certified to run Windows 7 or 8, you can load it on most clients.  Windows to Go (WTG) isolates the local drives to prevent cross data contamination.  This is nice feature while on the go.  You can even allow BYOD (Bring Your Own Device) for temporary employees. Just provide them with WTG and you can manage their computer while they are working on your system and they can have there computer back when they boot normally.

One of the questions from the crowd was how to handle deployment and patch management.  The response was to simply continue to use your current methods and manage the WTG installations as any other workstation.  Deployment is a bit different, but you can use either the installation media or a custom WIM image.

A lot of potential uses for the mobile and temporary work force with WTG.  Just a word of warning.  The WTG certified memory sticks get very hot after an hour or two.  If you are going to use WTG for longer periods, consider a WTG certified USB 3.0 hard drive.  Remember, it must support WTG.  The hardware must appear to the OS as a fixed hard drive.  Standard USB hard drives appear as removable.

Have fun and thank you to IWUG for another fun evening.

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more