Skip to main content

Class questions for 5118A on October 6, 2008

Question for class: 5118A
Class Date: October 6, 2008
Location: Lantech Training – Indianapolis, IN
Below are the questions that we had to place in the “Question Parking Lot.” We answered them in class but I want to share with my readers what our up and coming MCPs are thinking about.

Question:
Where can we get a copy of Standard User Analyzer?

Answer:
The Standard User Analyzer can no longer be downloaded on its own. Microsoft has moved it into the Application Compatibility Toolkit 5.0. You will also have to install the Application Verifier to get it to work. This move makes sense since its purpose was for developers to determine if their creations will work in Vista. As part of a migration team, we can use it to make sure our legacy applications can function in the Vista environment and to also help us find a way to make it work.

Downloads:

ACT 5.0: http://www.microsoft.com/downloads/details.aspx?FamilyID=24da89e9-b581-47b0-b45e-492dd6da2971&DisplayLang=en

Application Verifier: http://www.microsoft.com/downloads/details.aspx?familyid=d2dd7ee0-aaa2-402a-821d-43795d6cf139&displaylang=en

Question:
What are the memory limitations for Ready Boost?

Answer:
Ready boost is a way to increase the speed of your Vista machine. It was designed for systems with 512 MB – 1 GB to help them along. The rest of us can utilize them for performance enhancements as well. We do this by adding a USB key to your computer. When you insert the memory stick into the PC and auto play starts, Click Ready boost. The memory limits are 256MB – 4 GB. Microsoft recommends a 1:1 ratio on flash to system memory on lower end systems and a 2.5:1 ration on flash to system memory on higher end systems. The 4GB limit is due to the FAT32 partition on the flash drive. 4GB is the largest file size it can handle.

Comments

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

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.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Where did a User’s Account Get Locked Out?

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