silverhand

Dear guys, Just asking, when I setup SCCM for Update point, I did not know what someone had done WSUS Server Configuration Server before. So after deploying update patches, I got SMS_DISTRIBUTION_MANAGER error ID 2302, the package is used by different process. Should I remove both WSUS and SCCM Update Point and reinstall again? or is there possible way to fix or disable WSUS for running SCCM? Cheers, Thank you in advance for your help. Ted

Thank Peter, Sorry for my late reply. If you do not mind, could you please correct me following this deployment? Currently, we are running Curriculum network with IP address range as: 10.112.1.10 - 10.112.203.254, this is also our SCCM 2007 boundaries configuration. So, is it true that to avoid boundaries overlap, I just change the SCCm 2007 boundary to something, such as: 10.112.204.0 - 10.112.204.1. And then, I use the old boundaries as mentioned above for SCCM 2012. If so, do I need to stop WDS or anything before changing SCCm 2007 boundary? I know it is such a silly question, but serious, it make me learning a lot. Cheers. Thank you in advance for your help.

Dear guys, I am trying SCCM 2012 today, after following the guide from Anyweb, it was amazing, Just a silly question, I am currently running SCCM 2007, this setup for SCCM 2012 is just for my lab to try it, before I replace 2007 with 2012. But people said that I should not install SCCM 2012 along with SCCM 2007 which is currently running due to boundaries overlap. I am so confused about this point. Do I need to shutdown SCCM 2007 server and run SCCM 2012 for my lab? It would be a great help if you guys can help me clear this point. Be honest, I do not want to "play" hard with my SCCM 2007, I spent a lot of time to fix it all the time. So please go easy on me, if I did asking something really silly. Thank you so much for your help. Cheers,

Dear guys, Thanks anyweb! Sorry for my late reply due to busy in work! Finally, I tried to reinstall PXE and WDS service. And I found out the reason, WDS was configured before and located RemoteInstall in D: drive. But we had some setup folders like Packages (not RemoteInstall) in C: drive. I am not really sure because of this, so it made conflict to SCCM. But what I have done last weekend, it was just about to step by step remove PXE and uninstall WDS, and reinstalled later on. I also manually updated and reinstalled DP for all PKGs. And this morning, the boot machine showed that "ProcessDatabaseReply: No Advertisement found in Db for device smspxe". So the problem was related to our mandatory task sequence. And I also decided to install quickly a OS on new machine, and added machine name into AD, later on bingo, SCCM could show that Client=Yes and Approved=Yes. Seriously, I do not know whether machine is running wihout OS or somehow, SCCM cannot recognize the machine. So is it true that we need a preinstalled OS on machine before applying SCCM processes, such as: boot with PXE and apply our own OS with pre-installed softwares. Thanks you in advance, anyweb! I look forward to hearing from you. Cheers,

Dear Mikey C, It is definately awesome! I will try this next year when we run new machines for students! Cheers,

Dear anyweb, Thanks for your stop by! Sorry for my late reply, I have tried during weekend. All DPs are updated and the task sequence were used on right Boot Image. All other machines seemed work right, but except new machines. When I added them via MAC address, they are still showing that Client=No. I am not really sure due to this problem, so I cannot deploy my Windows 7 Image. I am thinking to clean SCCM from scratch The collections are not seem right for me now, clients are messy and I do not know what happened before with the technician before me. I am so depress about it now. The only luck was that I could deploy images on old machines with apply direct the task sequence on the target collection, otherwise I should hang myself. Thanks you in advance, anyweb! Hoping you can kick me an idea to handle this guy. Cheers,

Anyone can help? Or just give me an idea to deal with it Thanks you so much.

Hi bro, Did you mean that the boot image under OSD? Can you explain a bit about boot image crash? Like you could not deploy the OS or it just did not work. For me, I only have two image boot for x86 and x64, and I did not use default boot image from SCCM. Cheers,

I had Expired Certificate before, and it did not work when I created a new one, but SCCM did not work. And I had to remove PSP and WDS for recovering Distribution Point. Everything is seemed working fine, but everything the clients do booting, they show wrong architecture as x64. The message as in Aborted error: Downloaded WDSNBP Architecture: x64 The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved. Pending Request ID: 45 The technician guy before me, he installed RemoteInstall in C drive, I did not notice that and I installed RemoteInstall folder in D drive, I just tried to avoid system Windows Drive. And I also checked in IIS, I had two SMS_DP_SMSPKGC$ and SMS_DP_SMSPKGD$. SCCM also did not allow me to add new machine into collection, they stated them as Client=No and Approved=N/A. But as I said, the deployment can work properly every time I create collection and advertise the task sequence. How can I get rid of the message above and let the booting with correct architecture? If you have been experienced with this problem, please help me out. Thanks you in advance for your help. Cheers,I had Expired Certificate before, and it did not work when I created a new one, but SCCM did not work. And I had to remove PSP and WDS for recovering Distribution Point. Everything is seemed working fine, but everything the clients do booting, they show wrong architecture as x64. The message as in Aborted error: "Downloaded WDSNBP Architecture: x64 The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved. Pending Request ID: 45" The technician guy before me, he installed "RemoteInstall" in C drive (Windows Server 2008 R2 drive), I did not notice that and I installed "RemoteInstall" folder in D drive. And I also checked in IIS, I had two SMS_DP_SMSPKGC$ and SMS_DP_SMSPKGD$. SCCM also did not allow me to add new machine into collection, they stated them as Client=No and Approved=N/A. But as I said, the deployment can work properly every time I create collection and advertise the task sequence. How can I get rid of the message above and let the booting with correct architecture? If you have been experienced with this problem, please help me out. Thanks you in advance for your help. Cheers,

Just Update the post! I have recaptured the image from client machine with all necessary software (I did installation for Media class with multiple graphic applications). Import the new image to SCCM console, don't forget to update your Booting image and your task sequence with suitable OS image. Thanks you!

Dear guys, Sorry for another question post. I have done the image capture for my school machine, I thought it would be included all current installed software on that machine. But when I deploy the image to another machine, it was the same the original image without the software. I captured the image from a good client machine by removing it from domain, and process the capturing from the DVD. The image WIM file is really big, but after installation on another machine, it was exact the same our old image in 2011. Is it because of my WIM image file or is there anything wrong with my booting or reimaging process? Hoping you guys can help me to sort out this problem. Thanks you in advance for your help. Best Regards,

Hi Herrando, I got MP installation before. Do you have Lync Server installed on your server with SCCM? Double check whether all the SMS Page under Default Web Site in IIS. Cheers

Hi Morrisoki, So when you add the comment into deployment package indeed you run: "FEPInstall.exe /s /q ", but you will run "SilentInstall.cmd"? I have the problem when I capture the image, everything was included except FEP. Cheers,

Dear AnyWeb, This post is awesome! It helped me a lot. I just have a bit confusing about PXE booting. All my machines now could boot and run SCCM as normal, but the booting screen is still like below: Downloaded WDSNBP Architecture: x64 The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved. Pending Request ID: 45 Contacting Server: 192.168.3.1. TFTP Download: smsboot\x64\abortpxe.com PXE Boot aborted. Booting to next device... I tried to run on x84 Windows 7 platform. Is it anything missing that I need to take care about PXE boot? Thanks you so much! Cheers,

Dear AnyWeb, " Active Directory, DNS, DHCP Central Administration Site Server Primary Server " If our usage is just for small school, less than 500 machines, I believe that we do not need to implement CAS as people has concerned that CAS is somehow for a really big system. We are currently running two physical server for AD and SCCM 2007, and MS SQL Database in another VMWare machine. Can you suggest me the way to design new system for SCCM 2012? Do I need to setup a VMWare system for CAS? Thanks you in advance!

Thanks You Wdge! I found heap of information about SCCM 2012. If you don't mind, may I ask whether if we need to uninstall SCCM 2007 before install new SCCM 2012? Can you suggest some steps to ensure that we are good to go with SCCM 2012? Thanks you so much. Cheers

Thanks you for your information!

Dear guys, My apology if I posted something that we have mentioned before. But I just wanted to open a new thread for my personal case. We are currently running SCCM 2007, separated with DHCP server for a small school environment, and I has stopped working for a week due to expired certificate. After fixing like a week, the site status could be back to "Active", but I am not sure that if the problem 80004005 can be solved. My manager suggested that we could change to SCCM 2012. If possible, could you guys tell me whether I should upgrade to SCCM 2012 without uninstall it, or I should wipe everything and starting from scratch? I have followed Windows-noob steps to fix my SCCM 2007 up to now. So I really hope you can help me to clear this point. I am much appreciate for your help! Cheers

Hi guys, So before we try to install PXE Service Point, does WDS has to be able to start or run? Cheers,

Dear guys, I know this thread is pretty old, but I found it is still really useful. I have exactly the same problem. And I also tried to remove PXE Service Point and WDS again, and reinstall them again. But it is still error there. If you don't mind, could you help me to check the log file as below. Is it because of DisableRollback value? Thank you in advance for your help. PXESetup Log: <09-10-2012 10:45:04> ==================================================================== <09-10-2012 10:45:04> SMSPXE Setup Started.... <09-10-2012 10:45:04> Parameters: C:\PROGRA~2\MIE096~1\bin\i386\ROLESE~1.EXE /install /siteserver:SCCM SMSPXE <09-10-2012 10:45:04> Installing Pre Reqs for SMSPXE <09-10-2012 10:45:04> ======== Installing Pre Reqs for Role SMSPXE ======== <09-10-2012 10:45:04> Found 1 Pre Reqs for Role SMSPXE <09-10-2012 10:45:04> Pre Req MSXML60 found. <09-10-2012 10:45:04> No versions of MSXML60 are installed. Would install new MSXML60. <09-10-2012 10:45:04> Enabling MSI logging. msxml6_x64.msi will log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log <09-10-2012 10:45:04> Installing C:\Program Files (x86)\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi <09-10-2012 10:45:04> msxml6_x64.msi exited with return code: 0 <09-10-2012 10:45:04> msxml6_x64.msi Installation was successful. <09-10-2012 10:45:04> ======== Completed Installion of Pre Reqs for Role SMSPXE ======== <09-10-2012 10:45:04> Installing the SMSPXE <09-10-2012 10:45:04> Machine is running Windows 2003 SP1 or later. (NTVersion=0X601, ServicePack=1) <09-10-2012 10:45:04> WDS Service is installed. <09-10-2012 10:45:04> No versions of SMSPXE are installed. Installing new SMSPXE. <09-10-2012 10:45:04> Enabling MSI logging. pxe.msi will log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\pxeMSI.log <09-10-2012 10:45:04> Installing C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\pxe.msi CCMINSTALLDIR="C:\Program Files (x86)\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1 <09-10-2012 10:45:10> pxe.msi exited with return code: 1603 <09-10-2012 10:45:10> Backing up C:\Program Files (x86)\Microsoft Configuration Manager\logs\pxeMSI.log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\pxeMSI.log.LastError <09-10-2012 10:45:10> Fatal MSI Error - pxe.msi could not be installed. ------------------- pxeMSI Log: MSI (s) (6C:CC) [10:45:10:470]: Deferring clean up of packages/files, if any exist MSI (s) (6C:CC) [10:45:10:470]: MainEngineThread is returning 1603 MSI (s) (6C:9C) [10:45:10:472]: RESTART MANAGER: Session closed. MSI (s) (6C:9C) [10:45:10:472]: No System Restore sequence number for this installation. === Logging stopped: 10/09/2012 10:45:10 === MSI (s) (6C:9C) [10:45:10:478]: User policy value 'DisableRollback' is 0 MSI (s) (6C:9C) [10:45:10:478]: Machine policy value 'DisableRollback' is 0 MSI (s) (6C:9C) [10:45:10:478]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (6C:9C) [10:45:10:478]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (6C:9C) [10:45:10:478]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (6C:9C) [10:45:10:479]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (s) (6C:9C) [10:45:10:479]: Restoring environment variables MSI (s) (6C:9C) [10:45:10:480]: Destroying RemoteAPI object. MSI (s) (6C:08) [10:45:10:480]: Custom Action Manager thread ending. MSI © (8C:F0) [10:45:10:486]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI © (8C:F0) [10:45:10:487]: MainEngineThread is returning 1603 === Verbose logging stopped: 10/09/2012 10:45:10 ===