LimeLover

Hi OneOne, Yes, I just double checked and yes, I enabled the PXE boot on both images and deployed them. I just dont see them appear in the remote install folder.

Hi OneOne, I've tried this, but it still does not seem to work. When I look in C:\RemoteInstall I also do not see the SMSBoot images folder bieing created. Also when adding the PXE option to the DP it still gives the same error in the distmgr.log.

Hi guys, Im busy trying to install SCCM2012 on Windows Server 2012 using the SP1 update provided by microsoft to support this, but am running into some PXE boot issues. Please see the attached file for the log - There are some issues with installing WDS it seems. Does anyone have a solution for this? I do see WDS is installed in the server manager now but when I open the WDS console the status is "NOT CONFIGURED" See attachment for screenshot of distmgr.log

Hi guys, After following the guides here I am now stuck on something that could be quite simple: when creating the task sequence in step 7 in the guide I cannot select my deployed OS installer. I have double checked if the deployment went okay and retried it - it seems to be deployed alright. What can I do to make the OS installer show up in the task sequence? When I add it as an image instead of installer I see it just fine but I of course want to stick to the manual: http://www.windows-n...dows-7-x64-sp1/ could the manual be incorrect?

Hi all, I work for an MSP that is trying out SCCM 2012 to see if we can use it in our daily work, So far it seems like a pretty sturdy(but as always, difficult) product. I've been poking around with the SCCM guides on this website to use it as our local image DP so that we can easily deploy windows clients, which works like a charm! but I've been wondering on how to take this a step further. We have servers from our clients which are connected to the internet, mostly SBS 2008 and 2011 servers. These clients have a support contract in which we run updates each month. Of course, sometimes this slips under the radar and needs manual intervention each time(admin logs into servers, starts windows updates, checks if they completed and plans a reboot.) Of course we want to mimimize the times our admins spend on the servers for these simple automated tasks and also want a little more control over the machines. Does anyone have an idea on how we can manage these machines updates via SCCM 2012? My idea was to install the client in these remote machines, make a software/update deployment task that runs automatically and has a deadline so all these servers update the same night. But is this possible? Is this the best approach to solve this? Of course these machines all have their own domains and no trust with our SCCM machine(as this is of course impossible with SBS) Thanks!