Jump to content


Mikey C

Established Members
 View Profile  See their activity

  • Posts

    97

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by Mikey C

  1. Mikey C
    Have you tried using a Task Sequence? These are not just for OSD, as the name suggests they are simlpy deployments of a Sequence of Tasks. I would simply create applications for each one, and then put them in the correct order in the task sequence. It is not necessary to use the supersedence option, but it may be necessary depending on the Application. If you update the package content, and detection method for an application (specifically in your case, updated the Application with a different MSI) then the App will probably not be discovered any longer, and devices that App is deployed to will then run the Deployment Type (or Program in old school lingo). This may be an effective method to upgrade devices, so long as the MSI will happily install on top of existing devices without the need for a prior uninstall. This is not always the case though, so careful testing is required. But for many of our Apps (Foxit Reader Enterprise for example), we simply updated the MSI and then SCCM will evaluate the software as no longer being installed and run the new MSI, and update all devices that the Application is deployed to.
  2. Mikey C
    Well this is annoying!!!! It is now working. No changes to the TS were made except to add the 90 second delay (just a ping), which caused a number of failures on this device, but now it runs through fine. Could this have been an AD issue in my case, and in no way related to the issues other users are experiencing? If there were better logs for the bitlocker steps in the TS, this would be much easier.....
  3. Mikey C
    What do you mean "right into WDS"?? When you boot from SCCM boot media, whether it is flash drive, CD-ROM, PXE etc. it will boot up and show you the network options, then you choose which task sequence to run (which ever task sequences are deployed as available to PXE/boot image). If you don't want to choose which task sequence to run, then deploy it as required instead of available, that way the device will PXE boot, download the boot media, and kick off the TS after a 60 second prompt that you are about to replace you OS. Does that clarify?
  4. Mikey C
    Can you give us some more information to work with? What do you mean by WDS keeps taking over?! Are you referring to WDS on a different server, or WDS on the SCCM server because WDS should not be configured at all on the SCCM server.
  5. Mikey C
    Size: 233.36 GB BitLocker Version: 2.0 Conversion Status: Used Space Only Encrypted Percentage Encrypted: 100% Encryption Method: AES 128 Protection Status: Protection Off Lock Status: Unlocked Identification Field: Unknown Automatic Unlock: Disabled Key Protectors: None Found I ran the command within about 5 seconds of the wait command running, with the above - 100% encrypted, so that does not seem to be the issue (although i am confused as to why this would be an issue for anyone, surely the HDD is almost empty at this stage in a TS - isnt that the WHOLE reason why you PRE-provision?? So when the WIM is being applied, the data is already encrypted and so there is nothing to wait for?).
  6. Mikey C
    Either/Or. You should only use it once. I think i had used it in both B&C and deploy which caused a problem similar to yours. Also, have you got the steps in your TS in the correct order? You haven't accidentally dragged a step above/below another have you? To check, create a new Test TS entering the options in the wizard the same as your live TS, then check the order they are in.
  7. Mikey C
    Yeah, i assumed that must be where it should go, I already have a 90 second wait at that stage in the TS.... It makes no difference though, the Bitlocker pre-provision step succeeds (well i think it does, the TS doesnt bomb out), but fails at the enable bitlocker step. Other laptops (also Lenovo) running the the same task sequence are succeeding and have been since we started using bitlocker, so I don't think the problem lies there. But this eval device we have been sent, with the same tpm settings always fails and the only real difference i think is the SSD. Any other ideas Niall? While waiting for a response i will try flashing the BIOS to rule it out, but I am confident thats not going to make any difference. Thanks.
  8. Mikey C
    bump?
  9. Mikey C
    I always use SetACL whcih i find very reliable, i dont know that script. http://helgeklein.com/download/#setacl
  10. Mikey C
    Or if you want to do this on a larger scale for more apps: http://msdn.microsoft.com/en-us/library/windows/desktop/dd562082(v=vs.85).aspx http://www.microsoft.com/en-gb/download/details.aspx?id=7352
  11. Mikey C
    What OS is your WSUS server and what OS is your SCCM server? Have you patched your WSUS server? http://support.microsoft.com/kb/2720211 http://support.microsoft.com/kb/2734608
  12. Mikey C
    Can you post the ccmsetup.log and the client.msi.log (the latter is large, so post to dropbox/onedrive etc.)
  13. Mikey C
    The command line is in a batch file i take it? If it is not, then the variable %~dp0 will not work.
  14. Mikey C
    They are definitely not duplicated clients? So one or more device (hostname) one with client=yes and one client=no? We often get duplicates when re-imaging devices, so the old one will show as client no due to the reason Peter mentions.
  15. Mikey C
    I had this problem once with a Win 7 image. I needed to make sure that the build and capture had the OSDPreserveDriveLetter=false and the deploy put the OS on the next available partition which was referenced using a TS variable on the partition step. As long as those acre correct, it runs OK every time. Also, are you installing the sccm client using the PATCH= option?
  16. Mikey C
    Is the server running PXE and the DHCP server on the same subnet? Is the subnet the VM uses the same?
  17. Mikey C
    To troubleshoot this, you could try hard coding a value and seeing if the script updates AD with that information when run in the TS, that removes the TS variable being interpreted correctly from the equation. Inversely, you could add another command which interprets the TS variable and does something else, like just create a local text file to confirm it has run, that would avoid AD from the equation.
  18. Mikey C
    Tim, once you have captured the WIM, the device is in WinPE so it reboots into the full OS. The screen prompting for computer name, language, time zone etc. (out of box experience or OOBE) is completely normal!!! When deploying your captured image in a deployment task sequence, SCCM injects the information you enter in the relevant steps (apply OS, apply windows settings etc.) into the unattend xml file. So it sounds to me like you build and capture has performed perfectly and unlike some, you have nothing to worry about. Put your feet up!...
  19. Mikey C
    bump.
  20. Mikey C
    We are experiencing this issue also, on a 'high spec' laptop with an SSD. The Enable Bitlocker step is causing a failure with the exact same errors as in the logs above. It occurs irrespective of whether we tick the "Wait for Bitlocker to complete" box or not?? Can someone please tell me where to add this wait command that is the supposed workaround for this issue?
  21. Mikey C
    It is worth adding to this post i think, this issue seems to have been fixed with R2. You can now dump the contents of the ISO to an appropriately setup USB flash device and boot EFI successfully. No need to manually copy around EFI files.
  22. Mikey C
    I understand this is an old post, but still relevant to PXE in SCCM 2012 (in my case with WDS on Server 2012 R2). These two posts were instrumental in improving the situation: http://netecm.netree.ch/blog/Lists/Posts/Post.aspx?ID=57#.UwYmb_l_tnE http://wibier.me/pxe-boost-sccm-2012/ http://blog.uvm.edu/jgm/2010/11/04/tuning-microsoft-pxe-tftp/ http://windowsdeployments.net/how-to-speed-up-pxe-boot-in-wds-and-sccm/
  23. Mikey C
    Have I understood this question and answer correctly?? If you have a Windows Server 2012 SP1, running SCCM 2012 SP1, it is not supported to install the Server 2012 R2 upgrade?
  24. Mikey C
    Do you mean you installed kb2780664 or kb2854009? Also, I had a particular msi that i had packaged as an MSI which I could not get to work reliably consistently - it worked sometime on some machines sometimes, but not always (it was the Intel RST driver package and control panel). In the end, after hours of testing, googling error messages, i gave up and created a Package/Program instead of an Application, it just works - seems that the new Applications are too new, not as road worthy as the old method...
  25. Mikey C
    How did you fix it??
×
×
  • 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.