Jump to content


thepede

Established Members
  • Posts

    12
  • Joined

  • Last visited

thepede's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. My 960's have the Intel 82567LM-3 nic chipset. I have tried multiple driver combination's which have all failed. I have recently tried removing all the drivers from my boot image and it will still load the nic resulting in slow downloads. Since it seems the new version of WinPE is loading a default driver for the machine resulting in horrible latency. Is there any way to specify which driver to load for a given chipset? As I said using the previous version of WAIK my imaging was working fine. Any help is appreciated.
  2. I have recently upgraded my SCCM install to SP2 and have started having problems deploying images to desktops. Currently I deploy to Dell Latitude E6500's and Optiplex 960's. The applying image action is going really slow on the 960's for some reason, usually taking over 20 hours to deploy an image. A similarly sized image on the E6500's will complete in about 15 minutes. My smsts log isn't throwing any errors during the image process either. I'm not sure if this is an IIS issue or I need to update data in Config Mgr. If anybody has any input I would really appreciate it. Thanks
  3. thepede

    PXE boot problems

    Finally I have it working......what a relief!!! After many install's of PSP and WDS I took a closer look at my server properties in WDS for Boot. Before I had been using the pxeboot.n12 file from the SMSBoot\x86\ folder. I decided to try something different and choose the wdsnbp.com file instead and now I am connected and capturing my first image!!! Thanks for your help anyweb, cheers.
  4. thepede

    PXE boot problems

    I did thank you, what I had forgot was to add the boot.wim and install.wim from my 2008 server CD. After doing so I it starts to load files and comes up with the following. Windows failed to start. A recent hardware or software change might be the cause. To fix the problem 1. Insert your Windows installation disc and restart your computer. 2. Choose your language settings, and then click "Next." 3. Click "Repair your computer." If you do not have this disc, contact your system administrator or computer manufacturer for assistance. File : \Windows\system32\boot\winload.exe Status: 0xc0000001 Info: The selected entry could not be loaded because the application is missing or corrupt.
  5. thepede

    PXE boot problems

    Deleted the machine from the collection and imported again using the MAC address. Now I am getting the following. Download WDSNBP… Architecture x64 The details below show the information relating to the PXE boot request for this computer Please provide these details to your Windows Deployment Services Administrator so the this request can be approved. Pending Request ID: 5 Contacting Server: 192.168.1.2 PXE Boot aborted. Booting to next device…. PXE-M0F: Exiting Broadcom PXE ROM. Selected boot device not available I have made sure my Advertised task sequence is set to run as soon as possible, but still no luck. Nothing is populating in the machines PXE Advertisement.
  6. thepede

    PXE boot problems

    I changed the password for my account specified in WDS PXE filter but still wasn't working. I decided to try reinstalling WDS and I have made some progress not sure if it's forward or backward. After getting the message that it's contacting the server I'm given a message to press F12 for network service boot which I though was great. Until it got to the installation and gave me Longhorn Server images to choose from instead of kicking off my XP boot image. Any further help is appreciated. Thanks
  7. thepede

    PXE boot problems

    After running nslookup and querying my server it was not resolving correctly. I was able to fix that and DNS is looking correct now. Still hanging on contacting server through PXE unfortunately. WDSServer was listed with full rights for my RemoteInstall share. I am running DHCP on the same server as SCCM
  8. That may have been it, seems it was defaulted to 60 minutes. I have since changed it to 1 minute, but have not been able to test it yet. Thanks
  9. Hello, the guides were awesome as usual. I made it through the guide for deploying XP and everything went well except my client connecting to the server. I have checked the troubleshooting Windows PE booting guide and am still stumped. The furthest I have made it so far is to Contacting Server where it will sit and continue to fill the screen with dots until I shut the machine off. I checked the logs for smspxe.log and the server is seeing the client connect and soon after it says "Device has been accepted" and for each connection attempt on the client a new acceptance log message appears. I have so far been unable to find any errors for SCCM or WDS. Any additional help would be greatly appreciated. Thanks
  10. Sorry, didn't mention I initiate action on the machine policy each time. Don't know how long it would take if I don't initiate Machine Policy Retrieval.
  11. On average it takes about 30 minutes. It shows up in Collections for the machine first and usually 20 minutes later the machine will receive the notification.
  12. When we distribute applications through SCCM it seems to take quite a while for the advertisement to reach the client machine. In most cases installing the app is quicker then receiving the advertisements. Is there any to speed this process up other then initiating action on the client's policy which doesn't seem to do much. Thanks
×
×
  • 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.