Use PowerShell to control File Share Cache

This is a way to control the File Share Cache mode via PowerShell. Notice, that we are actually still using DOS. I went his route because to get this to work on a Server, you would have to install the Desktop Experience in order to gain access to the Offline Files API. I still had some difficulty with the Class Libraries and decided to go this route.

The one difference in each line is the final command: Programs, Manual, Documents, and None.

# Sets the Cache to:
# All Files and Programs that users open from the shared folder are automatically available offline.
# Also, Optimized for performance is checked.
([WMIClass]"\\lon-dc1\root\cimv2:win32_Process").Create("cmd /C net share PS /Cache:Programs")

# Sets the Cache to:
# Only the files and programs that users specify are available offline.
([WMIClass]"\\lon-dc1\root\cimv2:win32_Process").Create("cmd /C net share PS /Cache:Manual")

# Sets the Cache to:
# All Files and Programs that users open from the shared folder are automatically available offline.
# Optimized for performance is not checked.
([WMIClass]"\\lon-dc1\root\cimv2:win32_Process").Create("cmd /C net share PS /Cache:Documents")

# Sets the Cache to:
# No files or programs from the shared folder are available offline.
([WMIClass]"\\lon-dc1\root\cimv2:win32_Process").Create("cmd /C net share PS /Cache:None")

Comments

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

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

Jason Yoder, MCT

Search This Blog