[THIN] Re: PVS v SCCM virtual images
- From: Carl Stalhood <cstalhood@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Thu, 7 Jun 2012 20:11:20 -0500
In that case you'll probably need to press Shift+F10 to open a command
prompt and then cleanup the profiles under C:\Users. Delprof2.exe does a
good job.
On Thu, Jun 7, 2012 at 7:26 PM, Alan Tropper <Alan.Tropper@xxxxxxxxxxxxx>wrote:
> Hi Carl,
>
>
>
> Cheers I’ll give that a go, the error is when sysprep kicks in on the
> image it try to start up windows and then throws an error.
>
> What I’ve been doing is creating the image then selecting sysprep
> shutdown. The server does register against our KMS server so not seeing an
> activation issue with windows.
>
>
>
> Then when I take a copy of the image and start it up sysprep starts to run
> and its half way through here I get an unknown error when the windows
> splash screen is in the background.
>
>
>
> Cheers
>
>
>
> Al
>
>
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Carl Stalhood
> *Sent:* Thursday, 7 June 2012 6:29 PM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: PVS v SCCM virtual images
>
>
>
> As long as Windows is currently activated against a KMS server, rearm
> shouldn't be a problem. I've done it way more than 3 times. Run slmgr.vbs
> /dlv to verify activation. It should show you having 1 rearm left. If not
> activated yet, run slmgr.vbs /ato. Slmgr.vbs /dlv should now show 1 rearm
> left. Then sysprep should run successfully. I assume you're seeing the
> sysprep error before it reboots. Sysprep errors after it reboots are
> usually caused by local profiles.
>
>
>
> If the system is currently hosed, there are a couple registry keys under
> HKLM\Systems\Setup\Status\Sysprep that can be changed to enable sysprep
> again. I think Cleanup is 2 and Generalization is 7. Make sure slmgr.vbs is
> activated and try it again.
>
>
>
> On Wed, Jun 6, 2012 at 9:18 PM, Alan Tropper <Alan.Tropper@xxxxxxxxxxxxx>
> wrote:
>
> Hi Joe,
>
>
>
> After I amend the image for the 4th time when the golden image is
> re-deployed and it kicks into sysprep build fails with an unknown error.
>
>
>
> This is an expected issue but one I wasn’t aware of at the time, see link
> below:
>
>
>
>
> http://blogs.technet.com/b/askcore/archive/2011/05/11/sysprep-skiprearm-and-image-build-best-practices.aspx
>
>
>
>
>
> My image would have citrix installed and all I would do is re-name, join
> to domain and join to citrix farm….but now I need to look at another way to
> create my golden image and deploy.
>
>
>
> Cheers
>
>
>
> Al
>
>
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Joe Shonk
> *Sent:* Thursday, 7 June 2012 9:39 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: PVS v SCCM virtual images
>
>
>
> What issue are you having with re-arming? Also, SCCM and PVS accomplish
> two different things.
>
>
>
> Joe
>
> On Wed, Jun 6, 2012 at 6:29 PM, Alan Tropper <Alan.Tropper@xxxxxxxxxxxxx>
> wrote:
>
> Hi All,
>
> I am looking at building new citrix images as currently using ESXi with a
> citrix vmdk, however with win2008R2 and the sysprep issues of only
> re-arming 3 times (including service packs) this has left me to re-think
> how to deliver a citrix image.
>
> I have read a little about PVS and SCCM but was wondering how best
> everyone else handles this topic, any good links on how to configure these
> would also be a great help.
>
> Im looking at Xenapp6 Win2008R2 images while looking at upgrading to 6.5
> on the horizon.
>
> Thanks
>
> Al
>
> Alan Tropper
> Dept of Child Protection
> Wintel Engineer
> Tel: 621 76322
>
> This message may contain privileged and confidential information and is
> intended for the exclusive use of the addressee(s). You must not disclose
> this communication to anyone without the prior consent of the Department
> for Child Protection (DCP). If you have received this email in error,
> please notify us by return mail, delete it from your system and destroy all
> copies. DCP has exercised care to avoid errors in the information contained
> in this email but does not warrant that it is error or omission free.
>
>
>
> This message may contain privileged and confidential information and is
> intended for the exclusive use of the addressee(s). You must not disclose
> this communication to anyone without the prior consent of the Department
> for Child Protection (DCP). If you have received this email in error,
> please notify us by return mail, delete it from your system and destroy all
> copies. DCP has exercised care to avoid errors in the information contained
> in this email but does not warrant that it is error or omission free.
>
>
> This message may contain privileged and confidential information and is
> intended for the exclusive use of the addressee(s). You must not disclose
> this communication to anyone without the prior consent of the Department
> for Child Protection (DCP). If you have received this email in error,
> please notify us by return mail, delete it from your system and destroy all
> copies. DCP has exercised care to avoid errors in the information contained
> in this email but does not warrant that it is error or omission free.
>
Other related posts:
