[THIN] Re: Office 2003 install and cloning

Cheers !!!

 

Like to change the account to a domain account for ease.  Will look
tomorrow....Didn't notice that link at the top with that util when I was
looking earlier today.

 

Malcolm

 

________________________________

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Bob Coffman Jr - Info From Data 
Sent: 20 December 2006 21:39
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Office 2003 install and cloning

 

Sorry, I was logged into mycitrix when I copied that link. 

 

See CTX106393 or CTX111464.

 

 

        -----Original Message-----
        From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Malcolm Bruton
        Sent: Wednesday, December 20, 2006 4:24 PM
        To: thin@xxxxxxxxxxxxx
        Subject: [THIN] Re: Office 2003 install and cloning

        What's the knowledge base article number?  Link doesn't seem
valid.....

         

        
________________________________


        From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Coffman Jr - Info
From Data 
        Sent: 20 December 2006 19:08
        To: thin@xxxxxxxxxxxxx
        Subject: [THIN] Re: Office 2003 install and cloning

         

        Rick,

         

        Thanks for this information - you probably saved me a great deal
of grief. 

         

        I see Citrix has a tool to fix the CTX_SMAUSER and it addresses
some of the things you mention.   Find it at:
http://support.citrix.com/kb/entry.jspa?entryID=11780

         

        I'm testing cloning with newsid, and running ctx_sma.exe
afterwards.

         

        - Bob Coffman

         

                -----Original Message-----
                From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Rick Mack
                Sent: Tuesday, November 07, 2006 6:15 PM
                To: thin@xxxxxxxxxxxxx
                Subject: [THIN] Re: Office 2003 install and cloning

                Hi Matthew,

                 

                Sysprep should be ok. 

                 

                I've got to admit though that the easiest way to make
sure things are perfect is to install PS4 after the cloning process.

                 

                As an example of things that don't work out of the box,
hardware cloning plus Newsid will subtly break PS4 printing unless you
repair the DCOM and ICA listener permissions for the ctx_smauser. 

                 

                I've got a couple of scripts that do 98% of what's
needed if you're using newsid but until I can port the whole thing to a
VBscript it's still "work in progress". Anybody like a project?

                 

                regards,

                 

                Rick 

                Ulrich Mack

                Volante Systems, a division of Commander

Other related posts: