Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About RebelRenegade

  • Rank
  1. Is the server he deployed still on subnet A?
  2. You should not be setting any options on the DHCP server. Your cisco router needs an ip helper address for the DHCP server and PSP servers that reside in other subnets. it's possible that you need to update your site boundaries in SCCM.
  3. Defining the platform doesn't matter for PXE booting. PXE ignores that setting. If you make the advertisement mandatory, any computer that boots into PXE will run the task sequence without hitting F12 (good reason to put a password on your PXE boot). If you advertise it to all unknown computers, the task sequence won't run from windows. Computers with the SCCM client installed won't be unknown. Computers without the SCCM client won't see the advertisement unless they PXE boot.
  4. The task sequence won't run on anything until you advertise it to a collection. Plus, if you set the task sequence to only run on an old platform (see below), you won't have to worry about it accidentally being deployed to servers or end users. Assuming you don't have people still running Windows 2000 at least.
  5. I've tried running it as a command line "cmd /k %~dp0windirstat1_1_2_setup.exe /s" and used that command line as a program inside of a package and it just hangs like it's waiting for the program to exit. This same method works fine for other .exe installs. If I run that command in Windows to test, it works fine. smsts.log just says Waiting for job status notification... over and over.
  6. You need IGMP snooping enabled on all access switches, and multicast routing and PIM (IP services IOS) enabled on all L3 switches. Some switches will have PIM/mcast and IGMP snooping on them depending on your topology. So imagine a hub and spoke topology. Your core switch and WDS/SCCM server resides in the hub. And your core switch Switch A is connected to Switch B in another building on your campus. You route between Switch A and Switch B. In Switch A and B, ip multicast-routing distributed has to be enabled globally. ip pim sparse-dense mode is enabled per routed/VLAN interface. Verify with show ip pim neighbor and show ip pim interface. This is like show cdp neighbor for multicast routing. You should see your directly connected neighbor with the 1st command, and all interfaces with pim enabled with the 2nd. Now Switch B connects to switches C, D, and E in this building to provide access to hosts. Switches C, D & E need ip igmp snooping enabled globally. Verify with show ip igmp snooping mrouter. This will show the port that connects back to Switch B. Show ip igmp groups will show multicast groups that clients have joined. Even without an OSD running, you'll likely see hosts like network printers joining groups because of default settings.
  7. You can just use IsLaptop to deploy certain features that you want on your laptops as part of the OSD, like importing wireless profiles. If it's not a laptop, that entire group is skipped. You could do the same thing with Make and Model. What are you doing with Model# that you feel makes IsLaptop useless?
  8. The PE phase doesn't have full driver support. Sometimes you have to inject the drivers into your boot.wim. Instructions for doing that and enabling F8 command support are on this forum and also easily found on google.
  9. Looks like you might not be getting an IP address. Once you have the F8 support enabled, hit it so the computer won't reboot and do an ipconfig.
  10. Just whipped this up w/o looking over your entire list of requirements. It just includes Name, MAC Address and Interface Name, but you can easily add Model, Serial Number, OS and Service Pack to it. The other tables you want are dbo.v_GS_PC_BIOS.SerialNumber, dbo.v_GS_COMPUTER_SYSTEM.Model0 and dbo.v_GS_OPERATING_SYSTEM.Caption0. Don't know how to get SP level in there off the top of my head, but I'm sure it's under GS_Operating_System or something similar. SELECT TOP (100) PERCENT dbo.v_R_System.Netbios_Name0, dbo.v_GS_SYSTEM_ENCLOSURE.ChassisTypes0, dbo.v_GS_NETWORK_ADAPTER.MACAddress0, dbo.v_GS_NETWORK_ADAPTER.Description0 FROM dbo.v_R_System INNER JOIN dbo.v_GS_SYSTEM_ENCLOSURE ON dbo.v_R_System.ResourceID = dbo.v_GS_SYSTEM_ENCLOSURE.ResourceID INNER JOIN dbo.v_GS_NETWORK_ADAPTER ON dbo.v_R_System.ResourceID = dbo.v_GS_NETWORK_ADAPTER.ResourceID WHERE (((dbo.v_GS_SYSTEM_ENCLOSURE.ChassisTypes0 = '8') OR (dbo.v_GS_SYSTEM_ENCLOSURE.ChassisTypes0 = '9') OR (dbo.v_GS_SYSTEM_ENCLOSURE.ChassisTypes0 = '10') OR (dbo.v_GS_SYSTEM_ENCLOSURE.ChassisTypes0 = '14')) AND ((dbo.v_GS_NETWORK_ADAPTER.Description0 LIKE '%WIFI%') OR (dbo.v_GS_NETWORK_ADAPTER.Description0 LIKE '%Wireless%')) AND ((dbo.v_GS_NETWORK_ADAPTER.Description0 NOT LIKE '%Virtual%'))) ORDER BY dbo.v_R_System.Netbios_Name0
  11. I don't think it's possible to skip the step to install the SCCM client as part of creating an OSD Task Sequence. If the image is being deployed without a hitch, the client is installed as part of the process.
  12. What makes you think DC/DNS isn't working? The roles are listed. Roles install with warnings all the time. Can you browse the AD tree? Is Group Policy management available? DNS console? What happens when you ping lab.local?
  13. It's been a while, so I don't remember 100%. I don't think I had the tools installed for the build and capture. I had this same problem using a Hyper-V guest. No issues on a physical server. I just use a physical for the build and capture now.
  14. I don't know what your topology looks like so I'm going to make some assumptions. There's probably a distribution switch somewhere that has several VLAN interfaces that act as the default gateway for the VLAN various workstations sit in. Make sure the vlan interface for the vlan your test workstations are in have "ip-helper address xxx.xxx.xxx.xxx" commands applied. You can have multiple ip-helper addresses configured. One will be the DHCP server and the other will be the PSP. ip-helper addresses aren't required if the PXE client, DHCP server and PSP are all in the same subnet. Make sure the DHCP server doesn't have DHCP options 60,66 or 67 applied. Follow ibrafe's instructions for configuring a PSP.
  • Create New...