Saturday, September 3, 2011


Read this first...

Now.  Think about how this might impact network environments where the IT department, as a policy, packages and deploys such updates using their own tools (i.e. Microsoft System Center Configuration Manager, Symantec Altiris, etc.).  Ok.  So, if I follow their "Solution" I should wrap this turd in a perfume-scented script that runs it once, checks if exit code 1402 was returned, and then runs it again?!  I'm still sniffing this perfume scented turd, and it ain't smelling any better folks.  I'm sorry, but this is not a "solution".  I seriously hope someone inside Autodesk is working on a "Service Pack 1a"

No comments: