<p> I'm an Ops guy, I have a history of working in IT operations and I think of myself as a “technician” or “ITPro”. To be honest, I don't know what to call it, but my point is that I do not have a background as programmer. I've been talking with other Ops-persons about integrating and collaborating with developer teams for quite some time now. Trying to make others understand the benefits they can both give and receive when collaborating with developers and trying to convince operations teams that we have lots and lots to learn from developers.
On Knowledge Factory, the company I work for, every one get’s their own lab-server. Nothing fancy, but it helps a lot when I want to test something in a controlled environment. I’ve been playing around a bit with desired state configuration on my lab server lately. And especially with the great module VirtualEngineLab which I’ve been using to automatically build various scenarios. Each time I start a new build, the module uses the DSC resource xPendingReboot to check for pending reboots.
VBScript can feel like a thing of the past, but truth is a lot of companies have invested heavily in VBScript during many years. It all can’t be simply translated to PowerShell over a night. To get started with translating VBScripts to PowerShell, one way could be to break up the VBScripts into usable parts. This way we can start translating the Control Scripts to PowerShell and keep the using the VBScripts as is.
I was playing around with the cmdlets in the DFSR-module the other day and realized that none of them could (as far as I could tell) give me a reliable count on the number of items in the DFSR Backlog. My plan was to initiate a replication of two folders and then have a script monitor the backlog to generate status messages to keep me informed of the progress. I searched for a way to accomplish this by looking at the commands in the DFSR module that have the verb Get
UPDATE: Microsoft just announced that they have temporarily removed the update. For more details see: KB2830477 KB2830477 was released Tuesday November 12 2013 and updates the RDP Client on Windows 7 to RDP 8.1. After installing it we have experienced issues with Smard Cards no longer being available in the remote session. Uninstalling KB2830477 solves the problem. So if smart card authentication suddenly stopped working on your windows 7 clients, check if you got KB2830477 installed.