Jump to content


burnzdog

Established Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by burnzdog

  1. Hi All, Im currently building lots of packages that will eventually be slipped into the build process for Windows 7. I have an issue with a package I have created for Adobe Reader. If i run the command line manually it works fine on my win7 build: msiexec /i "AcroRead.msi" ALLUSERS=1 /qb /norestart TRANSFORMS="AcroRead.mst" I created a package and created the distribution point, then added to my Task Sequence. The install starts but just hangs during install. Few questions:- 1) Which package is best created for MSI installs via command line; standard package or by defination? 2) Is there any way to run the task sequence manually so that I don't have to rebuild the machine just to test the package? 3) If I update the command line of my package do I have to update the distribution point? Thanks
  2. Resolved - http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/4f21dc89-c4ca-4546-9e7f-37acfe062a76
  3. I know you have spoken about this in past threads but Im yet to find a working solution, and any help would be appreciated. Having an ongoing issue with booting from a laptop that Im testing with images. Got to the point now when I can no longer rely on "clear last PXE advertisement" nor does rebooting the WDS service. I have also tried changing the cachtimeout. The machine im using isn't, or shouldn't be in any of the collections. Whats interesting the log seems to think it exists? is there anyway I can check this? SMSPXE.log: [010.010.000.059:67] Recv From:[000.000.000.000:68] Len:548 14dddb0 smspxe 14/02/2013 11:24:21 3036 (0x0BDC) Executing LookupDevice(4C4C4544-0043-4B10-8038-B4C04F435731, B8:CA:3A:C6:8C:CC) smspxe 14/02/2013 11:24:21 4488 (0x1188) CDatabaseProxy :: LookupDevice succeeded: 852 1 852 1 smspxe 14/02/2013 11:24:21 4488 (0x1188) MAC=B8:CA:3A:C6:8C:CC SMBIOS GUID=4C4C4544-0043-4B10-8038-B4C04F435731 > Device found in the database. MacCount=1 GuidCount=1 smspxe 14/02/2013 11:24:21 4488 (0x1188) [010.010.000.059:67] Recv From:[000.000.000.000:68] Len:548 1941a30 smspxe 14/02/2013 11:24:23 3036 (0x0BDC) Ignoring req from [000.000.000.000:68] Dest Server:[010.010.000.040] smspxe 14/02/2013 11:24:23 3036 (0x0BDC) [010.010.000.059:4011] Recv From:[010.010.001.126:68] Len:548 16fe570 smspxe 14/02/2013 11:24:23 3036 (0x0BDC) [010.010.000.059:4011] Recv From:[010.010.001.126:68] Len:303 141d770 smspxe 14/02/2013 11:24:23 908 (0x038C) Executing GetBootAction(852, THOR) smspxe 14/02/2013 11:24:23 4488 (0x1188) No Boot Action for Device (852) found smspxe 14/02/2013 11:24:23 4488 (0x1188) ProcessDatabaseReply: No Advertisement found in Db for device smspxe 14/02/2013 11:24:23 4488 (0x1188) [010.010.000.059:4011] Recv From:[010.010.000.059:9000] Len:274 136e5f0 smspxe 14/02/2013 11:27:35 3036 (0x0BDC) Executing LookupDevice(46746E94-D140-497A-8C46-5463A8F006FD, FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF) smspxe 14/02/2013 11:27:35 4488 (0x1188) CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0 smspxe 14/02/2013 11:27:35 4488 (0x1188) MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=46746E94-D140-497A-8C46-5463A8F006FD > Device not found in the database. smspxe 14/02/2013 11:27:35 4488 (0x1188)
  4. THis is was fixed. It was a driver issue. I had to create a package that only had the working driver, rather than pointing it at the complete driver package.
  5. Hello Followed your guide for Build and capture Win7 Using SCCM 2007 SP3. We have made the Task Sequence to do the Build and Capture. Have chosen all defaults. Not added to domain. The system boots to pxe and the boot.wim. It installs the drivers and then right when it gets the the "Running Action: Setup Windows and ConfigMgr" task it gives the following error: "Task Sequence:BUILD failed with the error code (0x80004005). For more information, please contact your system administrator or helpdesk operator." Looking in the smsts.log file on the client i see that the installing drivers task completes successfully and then there are no errors listed. Is there any other logs on the server side i should be looking at? I have looked at the SMSTS.log and there are no "FAILS" "FAILED" or "ERRORS" Ive only just inherited the server and Im failrly new to SCCM but Im at a loss with how to fix this issue. Im assuming the boot.WIM isnt th eproblem as it get past that part. If I skip the "Install driver" task in the sequence it will run through and install the OS but nothing else. Have checked some similar links, and have: I have checked all these and there is nothing in here that I havent already tried: I have recreated the SMS install package. Left the License key blank. Toggled Drive install to install drivers specific to that model only. I have double check the account and its fine. Is there any more logs I can check that might show an error??? http://www.myitforum.com/forums/Failed-to-Run-Task-Sequence-0x80004005-m234645.aspx http://support.microsoft.com/kb/2586709 http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/70ae5fbe-d66a-48e1-8ad3-581137f6521d http://social.technet.microsoft.com/Forums/en-CA/configmgrosd/thread/abb9a372-a437-4b86-b98b-6895fa83275c Can anyone help?!
×
×
  • 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.