Jump to content


Rocket Man

Moderators
 View Profile  See their activity

  • Posts

    1009

  • Joined

  • Last visited

  • Days Won

    26

 Content Type 

Everything posted by Rocket Man

  1. Rocket Man
    Good Stuff! You have to extract the cab file to inject the drivers into the boot files. Once the cab is extracted you will have an x86 directory with the x86 winPE drivers for injecting into the x86 boot.wim and an x64 directory with x64 wnPE drivers for the x64 boot.wim. You have it working now anyway but just for future reference if creating new boot.wims!
  2. Rocket Man
    Mandatory = Required.
  3. Rocket Man
    Forget about the spanning tree idea so then. You do not have the correct drivers injected!
  4. Rocket Man
    This is SCCM SP1 looking at the boot.wim version. So the Dell WinPE4.0 should work, the winPE3.0 has been injected according to the driver version A12? Here is where the source of the winPE drivers are.
  5. Rocket Man
    It does sound like a driver issue. Have you verified that you are actually getting an IP address on the system prior to the reboot? You will have to enable F8 command support on boot images to test this.. If you are getting an IP address and can ping the FQDN of the site server/MP then you may want to take a look at this as it may very well be your problem if you have managed switches with spanning tree enabled on your network. Had a similar problem in my current setup but the problem occurred immediately with all HP machines. The spanning tree time frame was decreased from I think 15 seconds default (I think) to 5 seconds possibly. If it is the problem I would'nt recommend disabling the feature completely as it checks for loops on the network and automatically isolates the problematic ports. Other than this Im afraid I have nothing more to add as unfortunately I do not have any of these models in the enterprise so do not know if it is a common SCCM/Latitude E6540 problem or just a HW problem with the device you have at present.
  6. Rocket Man
    Good stuff !!
  7. Rocket Man
    You seem to have the the program deployment to only run if the user is logged on..... change it to run whether or not user is logged on and then it will be available in the TS editor. EDIT: Here is a similar post and solution!
  8. Rocket Man
    Have you tried using the x86 boot image in the task sequence as opposed to the x64 boot image?
  9. Rocket Man
    Hi I see the problem the & should only be the & symbol with NO semi-colon either.
  10. Rocket Man
    Happy new year one and all, bring on 2014, may it be a great year for all!
  11. Rocket Man
    How long are you waited before you have deemed it as unsuccessful?
  12. Rocket Man
    Yes you create a package from it. It should be a VBS script so give it a name to suit i:e promptforsystemname.vbs etc... There is no need to create a program for this package as you will be calling it via a run command Line task. In the TS editor, attach a run command line task directly after Disk Partitioning and tick the box to add a package (select the promptforsystemname package) and in the command line window enter in promptforsystemname.vbs OR whatever you have called the script. That's it. Once the disk partitioning is done the script will run and you will be required to enter in a computer name.. There are of course other more complex scripts available that have some validation checks (dummy proof) like non special characters allowed, no NetBIOS names may exceed 15 characters etc.. There are also other scripts with the use of MDT integration that can auto-name systems to the serial number of the system. This works good on most muti-national vendors but for some vendors it's a pain as some serial numbers are extensively long so the auto-naming fails, but with some script trickery you can overcome this, on most vendors (not them all as I have recently found out).
  13. Rocket Man
    hi there Don't want to hijack this thread but just a few things you may have or may not have done.. On the machines that are unsuccessful have you looked at the event viewer to see if it unfolds anymore information about the failed installs? Are these unsuccessful clients healthy clients within the 2007 environment? clean of malware, reporting correctly, etc etc.. Can you connect to the admin$ share of these machines from the site server initiating the client push? Do you have a standard local admin account on all systems that you can specify in the client push credentials like so %machinename%\account? Also 0x8007045a translates to: a dynamic link library (DLL) initialization routine failed Source:Windows Perhaps some different software/malware on the unsuccessful machines has messed up the dynamic link library in question that may need to be re-registered(maybe)? Here is a link that gives some further information into the error 1603!
  14. Rocket Man
    If it is only on 1 system you could check if the BIOS date/time is accurate on this particular device? Also check if the BIOS can be updated to newer version. There are winPE3.0 and 4.0 drivers for this model to inject into boot.wim on the dell website.
  15. Rocket Man
    And the updates you need installed during the B&C task is advertised to the collection that your B&C system is a member of? And you have configured the properties of the agent to SMSMP=fqdn.of.your.siteserver?
  16. Rocket Man
    There should be no files inside the WSUSContent directory as Jorgen mentioned previously also so I guess what you are seeing is correct. Are all deployment packages distributing and deploying successfully?
  17. Rocket Man
    As Jorgen mentioned you create a separate directory for all your different updates., this is good house keeping and keeps the different filters configured into separate deployment packages/source location(s). For example you should have a separate windows7 source directory for only windows 7 updates, windows8 source directory for only windows 8 updates, SCEP directory for only SCEP updates and so on..... You should definitely not point it to the WSUScontent directory.
  18. Rocket Man
    Had a similar problem with an upgrade to CU1... systems were not fully provisioned and the ccmsetup service was sky high in terms of memory demands etc.. Some clients were fine and the majority not. This was with both client pushes and OSD by specifying the path to the msp in the properties of the agent. Ended up upgrading to R2 and enabling the Hierarchy auto upgrade function.... fixed the problem right away, clients were fully provisioned and talking sense again. It is not an answer but it was definitely a solution to the problem.
  19. Rocket Man
    Thanks Niall.... that explains the change....
  20. Rocket Man
    Personally I feel that this would be correct considering that your WSUS source resides at your PS, thus the reason as to why you see details of the client pointing to yoursiteserver.fqdn. However i may be wrong.... but digging a liitle deeper into my own scenario, which happens to be the same setup as your own and probably 90%+ of all CM12 Hierarchies these days, I diagonsed the contenttransfermanager.log which I believe handles client download information. If I open any of these logs on a machine at a remote DP site it clearly shows that the client is downloading content from the local DP. just to be sure my SCEP deployment deadline is 12.00 each day and at 12:00 each day it shows the client downloading an ID like so : Persisted locations for CTM job {252152FA-2E26-4967-A0EF-4CB4ADB1092A}: (LOCAL) http://remotedp.fqdn/SMS_DP_SMSPKG$/81b9be19-49dd-4f1a-ba39-e451d7cfbfec time stamp at 12:00 This must be the daily SCEP definition deployed via ADR? I maybe wrong on this as I have only really started reading logs....and if I am wrong hopefully some-one else can contribute and elaborate some more on this... Just a quick question how many clients are at each of the remote DPs? You may consider deploying some MPs out to these sites and throttle the client settings down some so the communication is not as frequent.
  21. Rocket Man
    Resurrecting this old thread............ has anyone else noticed that the maintenance task for deleting expired updates has disappeared in SCCM 2012 R2? Maybe it is named something different, but nothing is sticking out, and I vaguely remember in SP1 it was named something like delete expired software updates or clean up old software updates or something similar. Now in R2 there is nothing that is sticking out that covers this maintenance task? Anyone else seen this..... site upgraded from SP1 to CU1 to R2...
  22. Rocket Man
    Yeah sure create the package (source files) as mentioned without doing it through SCCM. Place them on a network share anywhere and simply browse to the share and execute the batch file. Just to ammend the previous example I would also recommend putting in the %~dp0 syntax as you are running it from a share, so the batch file will look something like this: msiexec /i "%~dp0SupportTools.msi" /qb ping -n 11 127.0.0.1 copy " %~dp0NameofShortcut.lnk" "C:\Users\Public\Desktop" Also I forgot to mention that the batch file also needs to be in the source files package along with the executable and shortcut! Hope this helps...
  23. Rocket Man
    Simplest way is to create a package with the executable in it and also a copy of the actual shortcut. Then use a batch file as the command to line to install the software first then copy the shortcut also, so the command line will be the actual name of the batch file that execues the install and copy. So maybe something like this: msiexec /i "SupportTools.msi" /qb ping -n 11 127.0.0.1 copy "NameofShortcut.lnk" "C:\Users\Public\Desktop" That should do the trick!
  24. Rocket Man
    Did you edit your task sequence to attach your newly created boot image? Also is the SMSBoot directory created on the DP and populated with both x86 and x64 files.
  25. Rocket Man
    The question is how many rooms/labs are there in the district and how many deployments are targeted to the same system that is a member of the many different collections? I work in education sector myself and at present I have approx 12 campuses/schools managed by a single PS with approx 20 more to add. At present between 2 larger campuses, 4 large schools, 2 main offices and the rest of the sites there are approx 90-100 collections created with some odd 15 custom collections also. The main collections query AD to pull out systems from the OUs, so basically my SCCM asset management is a mirror of AD give or take some custom collections. But everyone's environment is different, but generally speaking in schools, computer collections tend to stay quite static(labs, classrooms etc..) and user collections can change quite frequent(staff,students etc..yearly) Having a rough educated guess at this......It sounds like that your systems are members of many collections...each with policies deployed, so this is why the applications maybe slow as they are running other policies from other deployments from other collections...if that makes sense.
×
×
  • 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.