|
Some of you wrote in to ask what my final resolution was on my SofTGrid, er App-V problem.
So, here's the scoop: I called Microsoft on Friday at 4.00,
and got a final resolution with a workaround by Monday at 3.00.
That's pretty darned awesome if I do say so. So, what didn't I know?
Here it is:
I had a "duplicate package GUID" problem.
See, every time you sequence a package, you give it a name of your
choice, and also associated with that package is a GUID that's automatically generated.
Except all my packages were coming out of the sequencer with ALL THE SAME GUID.
How did this happen? I was re-setting my VMware Workstation snapshot back
before every package, but what was I missing?
Turns out, if I had on my super-sharp night-vision Googles,
I mean goggles, I might have been able to find a snippet of text in this blog entry
http://blogs.technet.com/softgrid/archive/2007/08/21/inside-the-sequencer-part-1.aspx
Snippet from the blog:
"One of the most common questions I get at this point is: 'Can I install the Sequencer and then
create my image of the Sequencing workstation so that I do not have to reinstall it every
time I start a new Sequence?".
In short, yes.
The only time I ever saw an issue with this was with
a man from Georgia who installed the Sequencer component, opened it
and minimized it, then created his "snap shot" of the Sequencer.
Later he would "revert" to a fresh Sequencer and then maximize the
Sequencer component to start a Sequence. He did this about 10
times and then tested his SoftGrid Packages; none of them would
run. It wasn't until after extensive trouble shooting that he
revealed his process.
You see, when the Sequencer starts it creates a new GUID for the package. Because he
had snapped his image after having started the Sequencer every package had the
same exact GUID as each other."
Bingo. That was my problem. Except I'm not the "man from Georgia." I live in Philadelphia.
But my issue was exactly the same. Dang.
So, now my sequencer snapshot doesn't have the sequencer open. And things have been
(much better!) since I paid to get the final answer from Microsoft. Oh, and I didn't have to
re-spend the 20 hours re-sequencing my applications. There was a checkbox in the
"Save as" dialog which basically re-created the GUID. I was fixed and ready to go in about a half
hour after learning what my problem was.
Part 2: Get this tool (maybe before it's too late.)
NetPro has a neat new tool for AD change management. I've done only a liiiiitle bit of work
with this free tool, and it looks really neat. It puts
some "workflow management" around some common areas of Active Directory.
And did I mention, the tool is 100% free?
Except there's one (potential) problem: Netpro was just bought out by Quest. Hopefully this is a
good thing (I'm sure it will be.) But in the meantime, the status of this newly released
tool could be in the air.
But maybe it won't be if you download it and check it out and get your "Free Permanent License."
http://www.turbochargead.org/download/
Even if you might not want to use the tool NOW, if you THINK you might want it SOMEDAY,
I would suggest you take the three minutes and get this tool now, just in case.
Just my opinion.
|
