Sorry for the late response.
If you look at SCE as a whole, there's not a lot of activity for questions, etc. SCE isn't as complex as its bigger brothers/sisters and does fairly well without problems, for the most part. That said, what is your SCE client connection issue? From: Jon Harris [mailto:jk.har...@gmail.com] Sent: Friday, May 08, 2009 2:11 PM To: NT System Admin Issues Subject: Re: SCCM 2007 SP1 Sorry to hijack this but Rod which list on your site is better to ask for SCE client connection issues? The SCE list see's almost no traffic from what I see and almost all the others are more active. Jon On Fri, May 8, 2009 at 2:04 PM, Rod Trent <rodtr...@myitforum.com> wrote: You might hit the ConfigMgr list on the System Center community site if you haven't yet. http://www.myITforum.com/lists From: Chyka, Robert [mailto:bch...@medaille.edu] Sent: Friday, May 08, 2009 12:46 PM To: NT System Admin Issues Subject: SCCM 2007 SP1 We are having an issue with SCCM 2007 SP1. We are running it in a test environment to get it up and running until we put it on a production box in the near future. Here is the problem we are having: I was able to get Vista Sp1 working fine with Configuration Manager 2007 Sp1. I am able to build and capture an image perfectly fine and advertise and install software for it. But when it comes to Windows XP Sp3, when trying to Build and Capture WIM for XP, Configuration Manager is able to install XP and the program assigned from Task Sequence's options. When the process is occurring and Configuration Manager is trying to capture the Image, once the progress bar shows that Sysprep is installing, it gives an error ( XP failed with error 0x00000002). I have looked around and it seems there are ways for workarounds for it, but nothing official from Microsoft as where if updates were to come out, I don't know the extend or consequences of changing anything in particular, etc. Also, known problem with the drivers for HDD, for some reason it wouldn't take SATA AHCI Controller. Instead, it just accepts ATA. I don't know exactly how much advantage once will get with the advance features between AHCI and ATA, but from what I have read, it has been mixed responses from people over the internet and those that are Microsoft Certified that provide help in certain forums. So, for me in order to have gotten XP to be able to be installed from SCCM 2007, I had to change from AHCI to ATA in BIOS, then it went with no problem. But, Dell 755 and 760 have this default option, and is it something we should care or just go ATA, while better solutions comes out? So, besides this two problems , I think that this is working well, just that its time consuming. Has anyone run into this issue before? Any help is greatly appreciated!! ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~