Jump to content


n00blar

Established Members
  • Posts

    74
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by n00blar

  1. I've been reading the somewhat complete documentation on SCCM 2012, but I'm having a difficult time understanding the definition for: Package - Application - Deployment Packages - I think I have somewhat of an idea for "package" - a group of files that do not have an installation/setup routine (hence you can't run a setup.exe). Application, from what I gather, is a group of files that do have an installation/setup route (hence you can run a setup.exe/msi). Deployment package - I'm not even going to attempt it. Do applications become a package, or a deployment package, at any given time?
  2. So your Windows Deployment Server service is in "Started" mode, correct? In my case, the service was always stuck in "Starting..." mode.
  3. I had the same exact issue, and if none of the suggestions work, then this is the issue. Let me know if this helps.
  4. Okay, so there is known bug that may cause the above message in your environment. If you have access to Microsoft Connect, then you can see the reported RC1 bug here. Bug occurs as soon as PXE is enabled on RC1. There is a workaround to manually force PXE to work again, here are the steps: Disable PXE from Distribution Point in SCCM (uncheck PXE) Manually start WDS service if it's not running If service is hung up on "Starting", reboot your SCCM server Upon reboot, the WDS service most likely has started automatically [*]Enable PXE from Distribution Point in SCCM (check PXE) [*]If you have to reboot the server, you must do steps 1-3 all over again Hope this helps!
  5. If you do another server restart, after your last step, does the WDS service start again? I followed your steps, and WDS service started, but when I kept on doing server reboots, the WDS service gets stuck on "Starting". I believe there's a RC1 bug with PXE; I don't have this issue in Beta 2 lab, only with RC1. I have yet to be able to get PXE to work properly. So long as I remove the PXE checkmark from SCCM, the WDS service starts up again properly. As soon as I re-enable the PXE checkmark in SCCM, and I reboot the server...WDS service doesn't come up (it gets stuck in Starting...). I went as far as re-installing Win2K8 R2 on my lab and going through all the LABs, and the issue persists.
  6. Couple of questions in regards to this lab (mainly due to my lack of knowledge about this topic) 1. What are these UDA variables used for? 2. USMT, what settings are you collecting by using this? (I will read about this later on, as I'm not familiar with this either) Thanks!
  7. Looks like WDS service is throwing some errors for my install...and that may be the cause of my issues. 0xC1070107, going to look that up.
  8. Tried it and same message. I just don't understand what causes the issue. I never had this issue with your SCCM2012 Beta 2 articles, but this time around this issue seems to be persistent, and all the research I'm doing doesn't really point to a specific way of fixing it.
  9. Okay, this PXE is insane to troubleshoot. My previous update worked for two imaging tasks...I'm getting the same error message now. Looks like there's really no standard, or set, way to troubleshoot this beast.
  10. I seem to be having almost the same issue. I also double checked the steps shown above. The message I'm getting is: PXE-E53: No boot filename received PXE-M0F: Exiting Intel PXE ROM Operating System not found This message definitely seems to point something in CM, maybe I did miss something, but I just can't pin point it.
  11. Here's a message I've received as I was attempting to create a Software Update Group: The number of updates in the selected group exceeds the maximum allowed per deployment. The maximum number of updates for any single deployment is 500. Reduce the number of updates in this group to create a deployment. Interesting to know this...
  12. Is there a way to modify, add or remove, items once you've created the update group? I followed your steps, but later on I decided to 'add' more criteria, and I've not been able to figure that out.
  13. Hi everyone, Well, I've been a member of this forum for a short period of time, and I've asked way too many questions and gotten some good feedback from here and around the SCCM community. So, it's time for me to give back to the SCCM community. I modified a script that prompts for computer name as an OSD task is being performed. I've tested this script on a SCCM 2012 Beta 2 lab, and it's been working properly so far. Here's the link that explains how the script works as well as it shows the original owner and my modifications.
  14. I think I answered my own question. In SCCM2012 there's SSClient_DOMAIN@smsadmin_x.log file, which is located in %windir%\CCM\Logs folder.
  15. Did I miss something, but I don't see a log file for "application deployment" tasks?
  16. Pardon the hijacking... Will this also work with SCCM 2012 Beta 2? I tried the steps above, but I was never prompted for the computer name. I added the "Set Task Sequence Variable" right after "Apply Operating System" Thanks.
  17. Question: If one goes live using the RC version, do you think it will be possible to upgrade to the actual release when it comes out?
  18. Thanks for this great guide! Couple of questions: Is there a way to deploy an image and during the deployment process ask for "computer name", then use that computer name to join the domain? I was successful at joining the domain; I'd like to be able to 'ask' for a computer name instead of using a random one. [*]Can I disable the default local 'administrator' account and create a new user and assign local administrator rights to it instead? Thanks!
  19. Thanks for sharing! I had this issue and your post helped me fix this issue.
  20. Hi, I've followed these steps, but I'm having some issues with my lab setup, and I just can't think of a good way for fixing the issue that comes up. First off, I'm running my lab using VirtualBox. I have 3 VMs using an internal network, all three machines can communicate properly, so the network layer is working as designed. The only difference is that I have a dedicated server doing DHCP tasks. My DC provides domain services (172.16.16.2), my sccm2012 server (172.16.16.3) and a dedicated dhcp server (172.16.16.4). The VM machine that I'm trying to image from sccm2012 shows the following message on boot up: Sending ProxyDHCP request to 172.16.16.3... No filename FATAL: Could not read from the boot medium! System halted. Can anyone give me some pointers as to how to change this behavior? Thanks!
  21. Quick question. Does SQL Server 2008 have to be installed on the same machine as SCCM? Can I have SQL server running on a different server and have SCCM 2012 connect to it?
  22. Great guide! The only thing different I did was, in step 2 - I went with the default AD site (Default-First-Site-Name). I wanted to keep my lab environment as close as I could to my production environment, and so far seems to be okay.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.