Search the Community
Showing results for tags 'ip'.
Hey Guys / Niall - So I'm in the process of revamping our OSD build process and therefore performing a couple of new build & captures. After creating a pretty much standard task sequence (non-MDT) and having it install a couple of applications, I ran it. It performs 90% of the TS correctly as it applies the OS, installs applications, etc. When it reboots to capture, though; it fails when "Initializing Hardware Devices" - opening a command prompt shows no network adapters. I can understand not having the drivers on the boot image or for Windows, but why not at this point? It obviously has the boot image drivers or wouldn't have even allowed me to choose the TS and OS has drivers because it wouldn't have installed the applications. If I let the reboot time out, it boots in Windows mini-setup where after completing initial steps; I load Device Manager and everything's installed! SMSTS shows that it successfully completes the "Prepare OS" step but after that it's "winhttp failed" and "unknown host" So far I've tried this in Hyper-V using default & legacy NICs as well as trying on a 640 G1 - all with the same result. I've also tried using other boot images other than my default MDT x64 one with the same result. I also tried applying a Driver Package I built a while back which contains Win7x64 drivers imported from Hyper-V. The TS applies an OEM copy of Windows 7 SP1 x64 and I'm using SCCM 2012 R2 SP1 CU4. Any suggestions? Thanks!
Hi! How can i build a query based on a IP sunnet ? Address: 188.8.131.52 Netmask: 255.255.255.128 = 25 Network: 184.108.40.206/25 Broadcast: 220.127.116.11 HostMin: 18.104.22.168 HostMax: 22.214.171.124 I have now (but it won't do the job) : select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_NETWORK_ADAPTER_CONFIGURATION on SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.ResourceId = SMS_R_System.ResourceId where SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.IPAddress >= "126.96.36.199" and SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.IPAddress <= "188.8.131.52" Any tips, ideas ??
Hi All, First time poster. I have an odd issue and I am not sure it belongs under Windows 7, but I didn't see a better choice. The issue we are having is strange. Users running windows 7 on HP 4000pro computers are having issues with connectivity to one of our domain controllers. I say its with one because they can ping and contact other computers and servers on our Lan/Wan but cannot access the Domain controller on their local Lan. If we go into DHCP and block the IP they have assigned and renew the address with a new IP they then can connect. A few weeks later they will again have the same issue and we repeat the process of blocking and renewing with a new IP. The list of blocked IPs are growing and at the rate we will be out of IP addresses in 6 months. We thought it might be an issue with the built in NIC card so we purchase new card and installed them. We thought that fixed the issue but we just had 2 of the users with the new NIC card and these model PC have the issue repeat itself. The domain controller is a windows server 2003 which is being replaced in 2015. We only have 7 of these HPs. We have not seen the issue with any other models of computers on our network. We also have another office that is connected had has a few of these computer models, but has different domain controllers - and we have not had the issue in that office. Any suggestions on how I might resolve this issue? No I have not contacted HP. That is my next step.
Hello, I am currently seeing a limitation of SCCM 2007 with the number of IP’s assigned to a server. The number seems to be around 1,500 addresses. Can anyone else validate this or know of a way to work around this? SCCM see’s the servers; it just spends so much time in WMI getting all of the IP info and then dies before it can send the data back to the Parent SCCM Server. Any information would be greatly appreciated! Regards, Yarrokon