Jump to content


BRO-T

Established Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by BRO-T

  1. After deploying XP via PXE and a task list, on first log in I am getting 4 messages relating to 4 different Intel driver applications.

     

    Open file security warning.

     

    I need to some how accept this for all of these files, prior to users logging in.

     

    Have i missed something in the Task Sequence? Or have i missed something with the driver packages that are installed??

     

    Please help?

  2. ahhh, does that mean you can only re try the same machine after 60 minutes unless you restart the service? Or is it 60 minutes per PXE boot?

     

    Another thing that has sprung to mind is this, if your rebuilding a machine that SCCM knows about, you have to remove it first from SCCM otherwise it sees the mac address and chooses not to allow the PXE boot.

    Will simply deleting the client from SCCM fix this, or is there a clean up task/command to do this quickly?

  3. HI there,

    I have just got working PXE boot working again after having to remove the PXE service point and WDS. I also upgraded to SCCM R3

    PXE is working, I have built 3 machines by importing the computer information and 1 machine as an "unknown computer"

    The issue I’m having is that it took a long time for these machines to obtain the image advertisement. Bt this i mean, the 1st machine (All brand new from DELL) picked up the advertisement first time.

    2nd machine I kept getting abortpxe.com (i followed the guide to resolve this, still nothing) then after about 30minutes it decided to install.

    Same for the 3rd machine.

    The 4th machine (unknown computer) worked first time, yet the 2nd attempt with a different machine i got the same.

    It seems like i can only PXE boot 1 machine at a time. Is this correct? I'm under the impression i could build multiple machines at once??

  4. Hi all,

     

    I have recently just upgraded our Virtual SCCM server to R3. It was originally R2.

     

    I installed the Hotfix KB977384

    The prereq passed all of its checks,and then did the upgrade.

    It appeared to install fine, i had the success message at the end.

     

    I cant find anything to do with power management,

    and my management point now has a warning flag saying it has been degraded!!

     

    The server is 2008 R2 SP1

     

    Please help!

  5. Hi everyone, I really hope someone can help me.

     

    Our new phone system has a Unix box which exports the dialler stats to a NFS mounted share.

     

    I am using server 2008 R2 and have installed the NFS roles. I have created an NTFS share and tried to configure the NFS share. We have set the share to "Allow unmapped user Unix Access". as the Unix box is just creating a HTML file every minute with updated statistics.

     

    The problem I have is that only members of the local admins group can see these files. We need a variety of people to view them without being in the local admins group. Please help me!

  6. You can try this fix, reduce the cache size. Open regedit and navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\PXE (or for 64-bit OS, head to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\PXE). Modify the CacheExpire DWORD and set it to a lower value, in my case I set it to decimal value of 1, meaning that cache will only last for 1 second.

     

    Restart the WDS service.

     

    Further info here – http://support.microsoft.com/kb/2019640

     

    I also have this problem. After looking in the registry at the said location i don't have any values under PXE!!! Its empty!

  7. Hi there,

     

    I'm new to SCCM and I've inherited a working implementation which now has a few issues.

     

    I ahve started by building my own collections, OS images etc followign the website. I have got to the stage where i have PXEboot my 1st machine to build and capture the XP image. It gets so far, installs the OS, sofwtare, drivers, I believe it is failing on the sysprep task which is almost the last task.

     

    Can somebody please help, below is a sample of the SMSTS log file

     

     

    Administrator account name = 'Administrator' PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    Successfully retrieved the original password policy settings PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    Succesfully reset password policy settings on local machine PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    nStatus == NERR_Success, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\prepareos.cpp,797) PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    Failed to reset the administrative password, NetAPI Error = 2245 PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    ResetAdminPassword(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\prepareos.cpp,1368) PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    Unable to sysprep the machine, hr=80004005 PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    pCmd->Sysprep(bActivate, bMsd), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\main.cpp,270) PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    Sysprep'ing the machine failed, hr=80004005 PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    De-Initialization successful PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    Exiting with error code 16389 PrepareOS 21/10/2010 15:15:38 280 (0x0118)

    Process completed with exit code 16389 TSManager 21/10/2010 15:15:38 244 (0x00F4)

    !--------------------------------------------------------------------------------------------! TSManager 21/10/2010 15:15:38 244 (0x00F4)

    Failed to run the action: Prepare OS.

    Unknown error (Error: 00004005; Source: Unknown) TSManager 21/10/2010 15:15:38 244 (0x00F4)

    Sending status message . . . TSManager 21/10/2010 15:15:38 244 (0x00F4)

    Send a task execution status message SMS_TSExecution_ActionFailError TSManager 21/10/2010 15:15:38 244 (0x00F4)

  8. After a restart of the WDS everything starts up fine in the events log, but then i get these 2 messages;

    EVENT ID 258

    The description for Event ID 258 from source WDSIMGSRV cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

     

    If the event originated on another computer, the display information had to be saved with the event.

     

    The following information was included with the event:

     

    0xC1030104

     

    and;

     

    Event ID 512

    An error occurred while trying to initialize provider WdsImgSrv from C:\Windows\system32\WdsImgSrv.dll. Since this provider is not marked as critical, Windows Deployment Services server will continue.

     

    Error Information: 0xC1030104

     

    Folowed by;

     

    Event ID 521

    Provider WdsImgSrv was shutdown successfully.

     

    Then it syas everything else started fine. Have already changed the startup to automatic delayed start.

    This is a server 2008 64bit Virtual Machine.

  9. Hi all, this is my first post.

     

    I have used this site a lot to help understand Server 2008 and SCCM. Quick bit of history of where I am. I know some of the basics of SCCM and have now started a new job which I have inherited their SCCM server and setup so I'm still learning it.

     

    We have a problem with deploying images via PXE. On the client we get an error saying no response from server. A quick restart of the Windows Deployment Service fixes the issue, but to do this for every new build is not acceptable.

     

    In the event log this is the error message we are receiving

     

    An error occurred while trying to initialize provider WdsImgSrv from C:\Windows\system32\WdsImgSrv.dll. Since this provider is not marked as critical, Windows Deployment Services server will continue.

     

    Error Information: 0xC1030104

     

    Hope you can help me!

×
×
  • 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.