On a Microsoft MDT 2012 Update 1 installation that had worked during a test period we needed to deploy a new batch of laptops with a different product number as this batch was different from our tests because the fingerprint readers were removed from the device.
Archive for Automation Manager
During one of my projects we had to do a print migration of +500 printers and as this could become a repeating task during other migrations we decided to use RES Automation Manager to get this done. Read more
In most of our projects we use RES Automation Manager for task automation and as I’m a RES Certified Trainer I have to explain how RES Automation Manager works and every time I give this training I have to explain “Conditions” and “Evaluators” so I thought it would be a good idea to write a blog about these two options, their differences and their use cases.
During one of the projects I’ve worked on we did a Citrix XenApp deployment with RES Automation Manager, as we were using building blocks the deployment was up and running in no time. The usual software was installed on this server: Office, Adobe Reader, RES Workspace Manager and some other supporting components (Flash, Shockwave, Silverlight etc) and my initial tests came out positive but after installing the PVS Target Device Software I got a strange error when starting RES Workspace Manager while starting a new session:
I was working on a new Citrix PVS image for one of my current projects and the test before running the P2PVS.exe were good, all my apps worked like they should so I prepped the server for the imaging (preparing antivirus, last PVS optimizations and a full pre-scan of my VM) and I ran P2PVS.
I like to use the MDT 2012 database to store data to configure my servers, a lot of data can be hold in this database to customize and automate your deployment with MDT 2012 and with each release Microsoft adds more possible features and functions to this database. With the transition from MDT 2010 to 2012 Microsoft added a couple of things: