Jump to content


KeithDib

Established Members
  • Posts

    178
  • Joined

  • Last visited

Everything posted by KeithDib

  1. Rocket man, Yes I ran build and capture, all worked well during this. Peter33, drivers are good, if I right click in device manager and point to the drivers OSD has copied to the machine they install fine
  2. Peter33 The drivers were ripped/backed up from the same unit running XP before I started the process, also we have used the same drivers on other systems, so yes they are XP and tested And, yes. Unsigned is ticked, although again I have checked this both ticked and not ticked. As I say, the drivers copy to the target machine (as their all in a folder once imaged) but the system (or sysprep) does not seem to be installing them
  3. Peter33 When capturing I have only used the NIC driver nit a full set, sysprep package works fine as the changes I make in sysprep.inf are used, not sure how you could capture image twice?
  4. No, is does the correct things when running the driver package. Says 'downloading' then 'installing' takes as long to do this as the rest of the TS. Once the image deployment has finished and sysprep ran the system boots and these are folders in the root of C for each driver, numbered sequentially. I have tried with and without the WMI query, to test this and it makes no difference
  5. I have a new image, created using a Capture TS, this deploys fine and does all it should, apart from the drivers still It syspreps fine, deploys fine The drivers though will still not install
  6. I have not created an XP image before, so sorry if this is a dumb question.. When I create the image, should I sysprep before taking the image or not? thanks
  7. Thanks Rocket Man. I will change set up to use "Model" based driver packages and WMI query for this. What stage during the TS do you think its best to deploy this driver package?
  8. At the moment no.. I have set up driver packages, NIC..Audio etc etc, I have included these in the TS, I have also tried the TS auto Apply drivers but this created folders in the root of C: and put the driver files here in, but seems to do nothing with them
  9. Hi I have set up OSD but I am having trouble with drivers The image deploys OK, and the TS runs fine, but post install drivers will not work. My "Apply Device Driver" section of my TS seems to run (it downloads the drivers and says applying) but once the TS has finished the drivers are not installed. HELPPPPPP PS, I created the image from a sysprep'd machine with a PE boot disk to take image. Keith
  10. Hi Is there a list of third-party software vendors who's applications can be updated using SCCM 2007's Software Updates? Thanks
  11. Its OK, I've worked it out now and its working fine
  12. Hi Does this function work in Windows XP? I have tried but cannot get this working, what are the required steps? Thanks
  13. Set up 2 collections, one for machines that already have std on, the other for machines that already have pro on. Then install to these as required
  14. Hi Can you give more details of the package? Also check your package is downloaded to the client cache folder Keith
  15. After long talks with the software vendor, it now seems there is something in their .msi that does not work if delivered through SCCM, although it does work if ran from the client machine from command prompt!
  16. Hi When I run this report, under the column "Branch Distribution Points" all I get is a *... Why does it not list the BDP? Cheers Keith
  17. HI All settings are to install per machine, command line is below [changes app name and server name etc] I have also tried adding both ALLUSERS=1 and ALLUSERS=2, neither made any difference if installed through SCCM, but they did if installed using same command line localy. msiexec /i Application.msi /passive SYSTEMSCONFIG="\\ServerName\appclientconfig\EPDT"
  18. Hi all I have a package to deliver through SCCM. It is a vendor supplied .msi. If I install using a USB pen drive on a client machine it installs fine, installs as a per-machine install, shortcuts go in All Users desktop and "Start Programs" etc and shows in "Add Remove Programs" If I deliver through SCCM however it seems to install per-user but also is only appears int the "Add Remove Programs", the shortcuts are put into the current user profile and nothing is in "Start Programs". Also this application should put some files in "C:\Documents and Settings\All Users\Application Data", however when through SCCM these go into the current users Application Data. I have checked all switches etc and all are as normal. I am not sure why the swithces used from the command prompt on a desktop machine will work fine while the same ones wont through SCCM? I have tried both ways in SCCM, to deliver once to machine and for each user who logs on, with same results. Any ideas please? Oh were using SCCM 2007 v4.00.6487.2000 XP SP3 clients
  19. Hi I have now resolved the initial problem.. I can now WAKE the machines from "WOL magic Packet Sender" from either another test machine or the SCCM server, BUT SCCM will not wake the same machines? Any ideas? Keith
  20. I have only tried a couple (near by and not being used) and yes there all doing same.. all our BISO and drivers are upto date
  21. We have over 2000 of these machines on the network, trying with another maker is not an option for me Thanks for help though Keith
  22. Its a fujitsu Esprimo E5731, latest BIOS files installed etc The thing is I cant see how it can be BIOS related as it does work when newly plugged in... and as I say is I put machine to sleep it also works, its only after a shutdown. It dont matter if I go to Start/Shutdown or run shutdown from CMD either it still wont WOL...
  23. Hi I have tried this... It i shutdown windows correctly WOL does not work... If I pull plug then reinservt plug I can use WOL.... Its the opposite to what your would expect Keith
×
×
  • 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.