Search the Community

Hi all, So I had a working boot media. It would boot into the password screen where the network options would be visible. It would then pass through to the task sequence and complete the build as normal. However, upon updating the Distribution Points and creating a final boot media I no longer see the network options. Upon entering the password, the PC just reboots. Worth noting that if I use the boot media created prior to updating all the DP's, it all works (for now the IT Dept are using these). I just can't create new boot media should I need to, in this case was for a background change. I've tried the following: - recreating boot image - recreating boot media - updating MDT Settings and Files - Re-booting SCCM Server - I've been through all the settings and can't see that anything has been changed. Any ideas how to resolve this? Thanks..

Our environment contains a CAS site and 3 Site servers. Currently each site server has 1 DP and 1 MP. Because of a firewall and various security limitations, we are setting up a new DP, MP and update point that reports to one of the existing site servers. We use SCCM for OS Deployments. We Use Site Based boot media today. I do not see the benefit of selecting dynamic Media option when creating a boot disk because I still have to enter in a DP. So in my existing setup, does it just make sense to still use Site base media but have 2 boot disks for my one sccm site that has 2 MP and DPs. All the computers that report to the 2nd MP/DP will in their own boundary I haven't investigated what I am going to do with DP groups. Currently we don't use them.

Is it possible to build and capture in SCCM 2007 with static network info or am I just banging my head against the wall? I currently am trying to boot from media, enter network info, and trying to use the capture network to hang on to network settings through out. I have a feeling this futile though. I know I can build the machine and capture via media but I was hoping to do all though the TS. Any help is much appreciated. I wish our network section would just go to DHCP already and make my life easier. Mike

Whenever I create bootable media for any of my Task Sequences which were working there no longer is Task Sequence Wizard that comes up and ignores the whole process and the logs say that it found no "mandatory" assigned tasks so it quits. I have at least three deployments that are available, but it ignores it. I removed all the "unknown" devices to remove that possibility of it associating to those devices policies. Then I assigned it as mandatory and it works. Any insight would be great. I've tried recreating boot media, playing with Boundary groups, reassociating device collections/task sequences, etc. Any help would be greatly appreciate!!! Sincerely AnyNoob warbie smsts.log