Dan Newton

Posts by:
Dan Newton

Dan has been consulting, focusing on Microsoft infrastructure technologies, for over 15 years. He has worked with many of Atlanta’s fortune 500 companies and other enterprise customers throughout the US. Recent project highlights include: Server virtualization design and deployment to support over 300 servers across 10 server Hyper-V cluster Design, develop and deployment of migration from SMS 2003 to SCCM 2007 for SMS hierarchy comprised of over 350 SMS server support over 70,000 clients; Design of a global SCCM 202 hierarchy to support over 100,000 systems and internet-based clients

Follow Dan on Twitter

SCCM and Patching Internet Clients

Published: March 17, 2015   |   No Comments  |  Read more

We had a customer recently that needed to setup a second Software Update Point (SUP) to support internet clients. We ran into a strange issue after the SUP role was installed. The WSUSCrtl.log was reporting the following error: “system.net.webexcption: the request failed with the HTTP status 404”.

Functional Levels and PowerShell

Published: February 27, 2015   |   No Comments  |  Read more

We were prepping a global enterprise to raise their forest and domain functional levels to Windows Server 2012 R2. We wanted to know that ALL the DCs were seeing/registering the new level. So in comes my favorite scripting tool – PowerShell.

Rube Goldberg & patching the enterprise with SCCM – Part 2

Published: February 18, 2015   |   2 Comments  |  Read more

When patching (servers in particular) we recommend the use of Maintenance Windows (MWs). In SCCM Maintenance Windows are configuration “timers” that control the deployment of software and software updates. A given SCCM client can have multiple MWs and each are evaluated with a deployment is run on a given client.

Rube Goldberg & patching the enterprise with SCCM – Part 1

Published: February 17, 2015   |   No Comments  |  Read more

Deploying software updates to the enterprise is not unlike one of these crazy cool machines. A server downloads all the updates from Microsoft, the clients scan the server for new updates that are required, then the server will create a new list of updates to push, the updates are sent to Deployment Points and a new Update Deployment is scheduled to run…