Zak's IT Blog

PREFACE Sorry for the lapse in posts as of late. We're gearing up for a new school year and I've been a bit busy. It turns out this blog doesn't get an amazing amount of views a day, but it gets enough for me to know that it might be helping someone. I write these posts because I've always found myself having an unique issue that most forums do not answer specifically. So most of my posts are for specific issues rather than covering a broad subject. With that said I have a batch script that I wrote today to cleanup my file server. It's very rudimentary so bear with me. INTRO In the education environment you have children that leave the system every year. It's amazing what a child in the extent of a year can rack up in terms of roaming data. We use roaming profiles and folder redirection here for the students data. So every year our servers get loaded with 10s of thousands of files. Every year I used to go through the folders and adjust permissions and ...

This is an issue I've had a few times and when you look around on the forums you see multiple answers. I found the right one on an obscure forum that I can't think of right now. The quick answer is this: Use the correct version of DISM to service the image . They must be in the same "generation". For Windows 8.1 and Windows Server 2012 R2 this version is : 6.3.9600.16384 For Windows 8 and Windows Server 2012 and below this version is : 6.2.9200.16384 Background and Setup: I have a Windows Server 2012 box running System Center Configuration Manager 2012 R2. We are in the process of switching our primary OS for new systems to Windows 8.1 Enterprise x64. As I build my images the old fashioned I tend to forget a few things from time to time. In this case I built the image without installing the .NET feature. The instructions to do that are here: http://technet.microsoft.com/en-us/library/dn482069.aspx So I'm following the instructions to get a refresher on...

Today I got a call from a friend that was setting up WSUS on Windows Server 2012. He got WSUS setup but the clients were not checking in. After talking on the phone with him for a bit he told me he had not set anything up on the client side yet.  Here are the steps to setup your clients via GPO taken from  http://technet.microsoft.com/en-us/library/cc720539(v=ws.10).aspx In Group Policy Object Editor, expand  Computer Configuration , expand  Administrative Templates , expand  Windows Components , and then click  Windows Update . In the details pane, click  Specify Intranet Microsoft update service location . Click  Enabled  and type the HTTP(S) URL of the same WSUS server in the  Set the intranet update service for detecting updates  box and in the  Set the intranet statistics server  box. For example, type  http(s): //servername  in both boxes. Click  OK . This is great in most cases, but...