Monday, September 3, 2012
Table of Contents (Preliminary)
Friday, June 15, 2012
Microsoft TechEd 2012 - The Experience in Review
Key Take-aways for me:
- My skills are getting dated
- The changes coming with the 2012 products are vast and diverse
- Microsoft is changing their direction in some very surprising ways
- My skills are getting dated, but so are everyone else's now
| Hotel Room - Day 1 |
Day 1 - Registration, Breakfast, Keynote, Sessions, Lunch, Sessions and Beer
| Registration (not yet full, but would be full soon after) |
The Keynote
| Keynote session |
WCL327 - Maximizing Windows 7 Performance: Troubleshooting Tips - Johan Arwidmark
Lunch - (chomp chomp, slurp, mumble, burp, repeat...)
| Lunch (or Breakfast) |
WCL309 - What's New in Microsoft Deployment Toolkit 2012 (MDT) - Michael Niehaus
WCL302 - Alphabet Soup Deployment: From AIK to ZTI - Migrating from Windows XP to Windows 7 Using Nothing But Free Tools - Stephen Rose
| Beer! |
Day 2 - Breakfast, Vitamins, Water, Sessions, More Food and Beer
WCL303 - Microsoft Desktop Virtualization: The Right Technology for Your Business Scenario - Karri Alexion-Tiernan and Skand Mittal
Lunch - I'm a sloppy eater. I will spare you the details.
WCL382 - Deploying Windows 8 with the Microsoft Deployment Toolkit - Michael Niehaus
SIA312 - What's New in Active Directory in Windows Server 2012 - Dean Wells
SIA311 - Sysinternals Primer: Gems - Aaron Margosis
Day 3 - Breakfast, Sessions, Lunch, Sessions, Expo, Food, Beer again
SIA402 - How to (un)Destroy Your Active Directory - Ralf Wigand
SIA316 - Windows Server 2012 Dynamic Access Control Best Practices and Cast Study Deployments in Microsoft IT - Brian Puhl
- Brian was very candidate about the challenges inside of managing Microsoft's internal IT operations
- DAC is not a cure for all security management needs
- DAC is not a replacement for security groups
- DAC is a good enhancement to using security groups by extending a policy-driven approach to implementing template-based access management with delegation.
Lunch (you know the rest)
WCL404 - Turn PowerShell Commands into Reusable CLI and GUI Tools - Don Jones
BOF11-ITP - Windows PowerShell Best Practices - Ed Wilson and Don Jones
Day 4 - Final Day - Breakfast, Sessions, Lunch, more Sessions, Closing Party
WCL325 - Raiders of the Elevated Token: Understanding User Account Control and Session Isolation - Raymond Comvalius
WCL290 - Microsoft Application Virtualization 5.0: Introduction - Andy Cerat
Lunch - More obscene sloppiness and lost fingers
Hands-On Labs
WCL301 - Case of the Unexplained 2012: Windows Troubleshooting with Mark Russinovich
| Mark Russinovich at TechEd 2012 |
Closing Party: Universal Studios Theme Park
| Hogwarts - Harry Potter Adventure |
| The Hulk (part of it) |
| Getting on The Hulk |
Today, my colleagues and I boarded our Southwest flight back home to Norfolk airport and on to Virginia Beach. The picture below is from the Orlando airport food court near gate 102. It's a very nicely designed airport and the birds flying around the inside are a nice touch (none of them bombed us, as far as I could tell).
Conclusion
Thursday, July 28, 2011
Calling a URL from WinPE / DaRT Environment
So maybe you find a need to call a URL from a WinPE or DaRT session (yes, I know, DaRT is a modified WinPE), but without IE or a browser you find it a challenge. Fear not. There are options at your disposal.
Option 1 is to install a light-weight browser into your WinPE bundle, like Bart’sPE did/does. Firefox is a fairly common choice for that, but if you can get another browser to do that you have that option.
Option 2 is to invoke the XMLHttp object via script. You can do that with VBscript since wscript/cscript components are part of WinPE and DaRT. The nice thing about this is with XMLhttp, you essentially have a browser but without the GUI. You call URL's and even fetch (i.e. "scrape") the return HTML results if needed (I do that a lot and may post some examples soon). A command-line browser, sort of.
Here’s an example of option 2 – calling an ASP page with parameters…
url = "http://myserver.domain.com/loginfo.asp?c=Workstation123&os=Windows7&ts=Enterprise32b"
On Error Resume Next
Set ohttp = CreateObject("Microsoft.XmlHttp")
oHttp.open "GET", url, False
If err.Number <> 0 Then
wscript.Echo "fail: unable to open remote URL for asset number!"
wscript.Echo "fail: error is " & err.Number & " / " & err.Description
Else
oHttp.send ""
textData = oHttp.responseText
wscript.echo "info: completed"
End If
If error-checking isn't your cup of tea (or Four Loco), you can leave off the code from line no.4 to the end. The meat of this is lines 2 and 3 actually. Just create the object instance and call the .open method. That boils down to just the following...
url = "http://myserver.domain.com/loginfo.asp?c=Workstation123&os=Windows7&ts=Enterprise32b"
Set ohttp = CreateObject("Microsoft.XmlHttp")
oHttp.open "GET", url, False
Tuesday, May 3, 2011
VBScript Bulk Import for MDT 2010
ok, actually, the path that led me to Michael's article was like this: I downloaded MDT Web Frontend from Codeplex and played around with it. I emailed Maik Koster about how to make it capable of bulk/batch computer import and he pointed me to Mitch Tulloch's tutorials on MDT 2010 and the one (part 22 actually) on using Michael Niehaus' bulk import PowerShell script. Phew! See what happens when you fall down a slippery slope? Amazing things happen.
Wednesday, April 27, 2011
Imaging Computers with MDT 2010 and AutoCAD 2012
Microsoft Deployment Toolkit (MDT) 2010 is a FREE product that is aimed at helping System Administrators prepare and deploy custom operating system installations (images). I’m not going to explain MDT, WAIK or WDS here. There are too many other sites, books, and videos that do a great job of that. I don’t need to add any more noise there.
If you have network license AutoCAD clients and a network deployment share, you already know how that can save time doing repeated installations. You may also know how much it helps when pushing installations via SCCM 2007 (or similar products). Maybe you’ve tried bundling AutoCAD into your operating system image process but are using Ghost or some other snapshot process and find it less than ideal. Well, MDT not only provides an easier option, it eliminates much of the headache incurred with push installations.
For starters, MDT uses a sequential process to perform tasks (hence “task sequences”). Rather than running entirely under an unattended SYSTEM context with no UI, it runs under a user context (typically), so most of the prerequisite tasks of the deployment work just fine (unlike trying to push with SCCM, where the .NET Framework 4, and DirectX component steps fail). So you can run the default installation and simply add the "/W" parameter to use it with MDT 2010.
Caveats:
You may have better luck than I’ve had with using a “thin” image process and trying to install .NET Framework 4 as a task sequence package instead of going with a “thick” or “hybrid” client build*. In my experience, the .NET 4 installation via MDT task sequence never works. But you may be blessed. My approach is to include .NET components in the base image via a reference capture. It is crucial to have .NET 4 installed before attempting to install AutoCAD 2012 via an automated/unattended process or it will fail.
I only use network license deployments of AutoCAD when installing via SCCM or MDT. I do not ever recommend installing standalone/individual licenses
Steps:
- Build your AutoCAD 2012 deployment share ON the server where the MDT package will refer clients to (this works much better than building it elsewhere and then moving it and editing the deployment configuration INI files)
- Configure permissions on the deployment share to suit the user context of the MDT installation (if needed)
- Right-click the AutoCAD 2012 installation shortcut in the UNC folder (e.g. Acad2012.lnk), select Properties
- Copy the “Target” string contents
- Click Cancel to close the properties dialog form
- Open the MDT Workbench, expand the Deployment share, select Applications
- Add a new Application to the MDT workbench deployment group
- Option: Application without source files or elsewhere on the network
- Properties:
- Publisher: Autodesk
- Application Name: AutoCAD
- Version: 2012
- Language: (leave blank unless you really want to enter it)
- Details:
- Command Line: “setup.exe” (for now)
- Working Directory: Browse to the UNC share path (do NOT choose from drive letter!) make sure to specify the AdminImage sub-folder in the path (e.g. “\\ ServerName\Acad2012\
AdminImage”) - After created, click Finish
- Double-click the AutoCAD 2012 entry in MDT
- Click the “Details” tab
- Replace the “Quiet install command” text with the string copied in step 3/a (example below). Be sure to replace <uncpath> with your actual UNC path.
- Example: <uncpath>\AdminImage\setup.exe /W /qb /I <uncpath>\AdminImage\<
deployment>.ini - Click OK
- Right-click the Deployment Share in MDT Workbench and select “Update Deployment Share”
Assuming the rest of your MDT deployment share is configured, and you've already generated a suitable Boot WIM and Boot ISO file set, you should now be ready to start deploying AutoCAD 2012 with your images.
Notes:
1. If you discover (like I have) that you also need to install the DirectX components ahead of the AutoCAD deployment installation, you can add the Acad2012DX.msi package I’ve posted and set a Dependency within the AutoCAD 2012 application entry so it runs the DirectX installer first. If you do this, click “Hide this application in the Deployment Wizard” from within the MDT application properties for the Acad2012DX application item.
2. A return code of 259 from the AutoCAD installation can be ignored. I have not seen, heard or experienced any detrimental effects after that has occurred.
3. Because there is NO OPTION to disable desktop shortcuts for Design Review 2012 or Inventor Fusion 2012 via the Deployment Wizard configuration, you will have to resort to some trickery if you are required to keep shortcuts OFF of the standard desktop. My trickery is to add DEL commands to a script that wraps the main installation.
4. If you choose to enable the network log option, keep these points in mind:
a. The UNC path to the logs needs to have appropriate ACL and Share permissions granted to allow the remote installation context to make updates to the folder contents (log file)
b. It tracks the entire deployment bundle, but won’t be updated on the network share until the end of the installation process.
c. If the connection fails before the installation completes, the only trace of a partial installation will be in the client logs.
d. The network log is cummulative. It grows with each client installation. You may want to back it up, rename or delete it occassionally to recover space.
5. Why does Design Review 2012 get a “Autodesk” prefix, while Inventor Fusion 2012 does not? Consistency is important.
*terms borrowed from Johan Arwidmark and Mikael Nystrom of TrueSec (www.truesec.com) - geniuses on the topic of Windows deployment automation
Assumptions:
· MDT 2010 Update 1 with WAIK 7
· 32-bit Windows 7 client Deployment Image with .NET 4 included (sysprep’d from ref computer)
· New install (not a refresh, upgrade or replacement)
Script Code:
Paste the following code into Notepad…
@echo off
TITLE Installing AutoCAD 2012
CLS
echo installing AutoCAD 2012...
SETLOCAL
SET XLOG=%TMP%\Adsk2012_Setup.log
echo %DATE% %TIME% installing autocad 2012 from network deployment >%XLOG%
rem ------------------------------------------------------
rem beware of word-wrapping below. should be on one line...
rem ------------------------------------------------------
\\SERVERNAME\Acad2012\
rem ------------------------------------------------------
echo %DATE% %TIME% cleaning up desktop shortcuts... >>%XLOG%
del "%public%\Desktop\Autodesk Design Review 2012.lnk" /f /q
del "%public%\Desktop\Inventor Fusion 2012.lnk" /f /q
echo %DATE% %TIME% desktop shortcuts removed >>%XLOG%
ENDLOCAL
Edit the code to replace SERVERNAME and other info to suit your needs. Save the Notepad file as setup.cmd somewhere on the MDT server (e.g. E:\Apps\Scripts\Acad2012\
Import into MDT 2010 deployment share:
Right-click Applications, select New Application
Select type: “Application with source files”
Specify the properties (publisher, product, version)
Select the setup.cmd file (click Browse)
Confirm, import and click Finish
Open the Application properties, copy the “Application GUID” value to the clipboard
Open Deployment Properties, click Rules tab
Add to [Default] section…
; autocad 2012 custom deployment
Applications001={paste the application GUID here}
If you already have other ApplicationsXXX entries, just insert it after the highest number and assign the next sequential number (e.g. Applications011={guid} )
Useful Links on MDT 2010:- TrueSec - http://www.truesec.com/infrastructure/tools
- Zero Touch Deploy - http://www.zerotouchdeploy.com/
- Windows Networking - http://www.windowsnetworking.com/articles_tutorials/Deploying-Windows-7-Part1.html