Jump to content


Search the Community

Showing results for tags 'network'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

Found 6 results

  1. 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..
  2. Hello, I am fairly new to Config Manager and would like some guidance from the pros. Running into an issue when creating Task Sequences for OSD. When i go to deploy the TS, the last page/tab has an alert "A network access account is required to access content from Windows PE" and there is only one option from the drop down, when there used to be two (see pic). I have a NAA setup and verified, and the deployment of a previous TS did not have this issue (10 minutes prior to creating current "problem" TS). I have deleted the TS, NAA, tried a different NAA and TS, but still have the issue. Any help would be greatly appreciated. Thanks
  3. Afternoon, Recently, I have noticed that some our machines are not consistantly joining the domain as part of the task sequence. I find the issue is very strange, for example the same laptop can take multiple attempts before finally going through and completing the task sequence. The issue occurs with different laptop/desktop manufacturers and models. It also occurs with machines that have previously been sucessful through the task sequence. Our setup has been in place for 18 months and the task sequence has not been altered. The boot image has also not been altered and the correct network drivers are present. I have read that the network drivers in the driver package may need updating, however as the machines will occasionally work I am unsure as to whether that is the correct answer. Within the task sequence I have checked that the user account used to join the machine is correct and it has appropriate permissions. After reviewing the SMSTS logs I have noticed the following: Found network adapter "IntelĀ® Ethernet Connection I217-V" with IP Address 169.254.101.136. TSMBootstrap 04/06/2015 12:32:50 2920 (0x0B68) So I think it must be failing due to the IP address. I am unsure as to why a 169.254 address would be issued. Can anyone explain why it picks up this address during the image build? Towards the end of the SMSTS log I can see the following: Retrying... TSManager 04/06/2015 12:47:36 2972 (0x0B9C) CLibSMSMessageWinHttpTransport::Send: URL: sccm-vm-wm1.XXXX.co.uk:443 CCM_POST /ccm_system_AltAuth/request TSManager 04/06/2015 12:47:36 2972 (0x0B9C) In SSL, but with no client cert TSManager 04/06/2015 12:47:36 2972 (0x0B9C) Error. Received 0x80072ee7 from WinHttpSendRequest. TSManager 04/06/2015 12:47:36 2972 (0x0B9C) unknown host (gethostbyname failed) TSManager 04/06/2015 12:47:36 2972 (0x0B9C) hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8936) TSManager 04/06/2015 12:47:36 2972 (0x0B9C) sending with winhttp failed; 80072ee7 TSManager 04/06/2015 12:47:36 2972 (0x0B9C) So I google'd the above and it is effectively telling me that machine can not speak to the DC in order to join the domain. Which makes sense as it has a 169.254 network. Hopefully someone may have seen something like this before. It is starting to cripple our productivity. Please let me know if any further information. Thanks in advance. Stephen
  4. Let me start by saying Thank you! for writing such awesome tutorials - you guys rock! I have somewhat of a unique (at least I think it's unique) situation. I have several remote sites that all have their own local ISPs - these sites are not networked to the point of being able to access the CAS directly. We are using Win 7 Enterprise so we can take advantage of MS DirectAccess and/or a 3rd party zero touch VPN client. My trouble(s) are this: I need to upgrade some Windows XP SP3 machines that reside in these 'independent' sites to Windows 7 Enterprise. I have created a TS on Standalone DVD Media which, in testing, works great with one exception: I can not seem to migrate the TCP/IP info from target machine into the newly imaged Win7Ent build. Each machine has a static IP address that must be reapplied in order for internet access to function. Per a company security policy, these sites do not have DHCP working locally. In my testing, I have not been successful in migrating the static TCP/IP values. In my TS, I have the enabled the setting under Capture File and Settings> Capture Network Settings > Migrate network adapter configuration... not sure why its not reapplying the configuration? I read in TechNet that if this is enabled, it should overwrite the step "Apply Network Settings" > "windows will configure network adapters to use DHCP by default..." sidenote: I also have the TS trying to migrate computername which is also not working as I believe it should. While this is not terribley important, it would save me some extra time when I have our helpdesk come back around and touch the machines to reinstall some peripherals which our locations must use.
  5. Hello All, I'm trying to image a Dell Precision M6800. It PXE boots and pulls the boot wim fine but once it gets into the task sequence area it will just reboot. I can't seem to pull an IP address to it at all but it PXE boots fine. This is the only laptop that does this. Even the previous M6700 will boot via PXE and is able to image. I also have booted into all other Dell Machines fine. This is the first M6800 and its not letting me imagine it. I can't seem to figure out what is wrong. Is any one else having this problem with other computers? smsts.log
  6. Hei all, I am having a truly strange experience with our SCCM2012 server and a OSD to some desktops. Now, if I had just started with them I would have thought that I had the incorrect driver, but thats not the case here. About a month back I started to configure replacement client desktops for the students. These machines would be going to the library, an intense environment for data. So to make things simple for myself, I took some old HP dx2250 Athlon pc's, installed a new PCI Wifi card and imaged them from SCCM with Win7 x32. I have completed all of them, no problem. I then decided to expand on the usable machines and place several more in the common areas. First batch went well. But the second batch hit a hitch. When they were loading the WinPE environment, they repeatedly rebooted when the network drivers were been loaded. The machines are IDENTICAL in every way to the ones that had been imaged before. I tried booting them on different vlans, but the same issue happened on all. Finally I took one of them over to my work office to troubleshoot it and low and behold - it worked. I did no changes, just booted it from a different physical location. The vlans here are the same as in their previous location. And now things go really weird. I brought over the last 3 and two of them did the same as the first. But not the last. No matter what I try, I cannot get the WinPE environment to load past the network driver load. As mentioned before, the machine is identical to all the others that have been successful. Are there any logs that I can check to follow up or do any of you have any tips for me? Cheers & thanks in advance! Anthony
×
×
  • 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.