Simple RoboCopy Function for quick transfers

When Rebooting Is Not The Answer

A couple of weeks ago I got to thinking, I do these little robocopy transfers all the time why not write a function so I can do a transfer and I don’t have to go looking up all the parameters.  So after a few minutes, the below script was born.  Simply run the script in Powershell, and it will prompt for the old folder (source) and the new folder (destination).  Once the copy is complete it will monitor the source directory and copy any changes until you exit the script which is great when a user is still working in the source directory such as when you need to move a home directory.  It also sticks a log file in the directory you ran the script.  Just keep in mind that this is setup to be a mirror copy and if you reverse the source and destination you will copy…

View original post 81 more words

Quickly fix Windows is not Genuine from different Windows versions.

When Rebooting Is Not The Answer

I had an issue today with an old KMS server that some machines had been talking to getting shut down and then the machines months later complaining that they couldn’t find the KMS server.  I  then removed the KMS server’s DNS entries and prevented it from publishing them to dns which had been missed before.  That isn’t the purpose of this post though so if you need more info the below two links help out a lot.

How to remove a KMS Server from your Infrastructure

Additional info for Server 2008 only.

Back to the purpose of my post was when I get tickets for activations (as I have over the past few days) I wanted an easy script to run slmgr, remove the product key, input, and activate the new key.  We use MAK keys in our environment so just for the few machines that were set up for…

View original post 121 more words

Alternate Names for File Servers

When Rebooting Is Not The Answer

I had a server I had to quickly give a alternate name to so that the existing users could point to the new server but I didn’t want to rename it the same as the old one.  Traditionally you would simply add the following registry entry.

Registry location:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters
DWORD name: DisableStrictNameChecking
DWORD value: 1

Problem is this only works if you have SMB1.0 enabled on both the server and client and you know how unsecure that is (think EternalBlue exploited by Wanna cry).

The proper way is to use netdom to add an alternative name by doing the below.

This will add a new SPN in active directory for the current machine name.

Special thanks to Dimitri’s Wanderings which is in the first link below as that saved me a lot of time.

https://dimitri.janczak.net/2016/09/26/multiple-server-names-on-windows/

https://support.microsoft.com/en-us/help/3181029/smb-file-server-share-access-is-unsuccessful-through-dns-cname-alias

View original post

Getting email alert and smsts log when imaging fails via PowerShell

When Rebooting Is Not The Answer

So in follow up to my last post I have been testing a script to look for the smsts log when the task sequence fails and send me an email with the smsts.log as attachment.

I set this up in my MDT task sequence under the gather logs and statestore on failure section so that way whenever the task sequence has an error I get the logs.

I have a nice array of locations of the smsts log and a foreach loop to look through them test if they exist using Test-Path cmdlet and attach them to my email.

Seems to work well from what I have seen so far.

View original post

SCORCH : An introduction to Orchestrator – Schedules

Schedules enable you to define when a Workflow or Activity can run. For example, there may be times when it is inappropriate to run some Workflows, such as running a backup Workflow on a main server during regular business hours. 1. Checking a Schedule This Workflow uses the Check Schedule Activity to match the current … Continue reading SCORCH : An introduction to Orchestrator – Schedules

SCORCH : Remediating SCOM Alerts Using Orchestrator

IT Snacks!

One of the most effective Orchestrator runbooks is the ability to remediate SCOM alerts, If you receive a certain SCOM alert and you used to solve it following manual tasks everytime, you can create a runbook which can automate it all..

It is assumed that there is a SCOM server up and running monitoring an IIS8 website and integrated with SCO.

without further ado let’s jump in :-

This is the final runbook we are going to create and I will walk you through some activities :-

01

As you see we are going to create a runbook that will investigate the stoppage and the unavailability of an IIS 8 website, without Orchestrator you used to ping the related server, check IIS services and make sure they are all up and running, we can make all that in one runbook to ping the related server and to check for any stopped…

View original post 426 more words

SCORCH : An introduction to Orchestrator – Computer Groups

System Center 2012 – Orchestrator is designed to interact with all of your data center systems. Computer groups let you target selected activities against a set of similar computer systems instead of a single computer. By configuring the activities in your runbook to use a computer group, you have the flexibility to add computers dynamically … Continue reading SCORCH : An introduction to Orchestrator – Computer Groups

In telemetry we trust?

More than patches

Telemetry is one of those things that tends to divide a room. On one hand it’s productive and accurate feedback for your product of choice and on the other hand it’s big brother spying on what you’re doing in that product. I wanted to share a recent experience with you based on my recent upgrade of Microsoft System Center Configuration Manager (SCCM) to the recent 1710 release as it may make you change your mind.

The long awaited 1710 release was made available last week a little before midnight in the UK on 20/11/17 (or 11/20 in the US Smile). The next morning I fired up my lab which runs the current branch version of SCCM, ran the early update ring PowerShell script and proceeded to whizz through the wizard in a speedy not hastily fashion. This was lab after all so on with the day job and I’ll check…

View original post 689 more words