Jump to content


Jorgen Nilsson

Moderators
  • Posts

    481
  • Joined

  • Last visited

  • Days Won

    30

Posts posted by Jorgen Nilsson

  1. Hi,

    Is it the same computer model you are trying to image? Are you using unknown computer support?

    DHCP Options should not be used, when PXE booting a device that runs UEFI instead of Leagcy BIOS it will fail as the boot file name is different from the one you are pointing on..

    Regards,
    Jörgen

  2. HI,

    IT is not possible with an Application at all as the detection method will check it it is installed and never run again. So you cannot use an application, a Package/Program will be the way to do it, and as you didn't want any suggestions using a GPO instead, I recommend that you have a look at using a schedule task instead :-)

    And this really is a good idea as the SCCM client is set to delayed start so if you start a comptuer and log on straight away the service hasn't started yet so the program will not run.

    Regards,
    Jörgen​

  3. Hi,

    No that is not needed except for in this rare scenario "Replication between a central administration site (CAS) and primary sites may be blocked after you upgrade the CAS to System Center 2012 R2 Configuration Manager Service Pack 1. This problem only occurs in environments that have tens of thousands of deployments for legacy software distribution packages. When this occurs, the Offer Manager component on the primary site server will appear to be stalled the Offermgr.log file on the primary site server seems to be "stuck," and no log entries are recorded in the Offermgr.log file. You can install Cumulative Update 5 to prevent this issue from occurring.

    Regards,
    Jörgen​

  4. Hi,

    What server OS are the DP that is used to PXE boot from using? Windows 2008 R2 doesn't support PXE booting 32 Bit-UEFI devices for instance so that can be one factor.

    Are you using DHCP Options or IP Helpers to point out the PXE server? IP Helpers is the only thing that will work, if you use DHCP Options and specify the boot loader it will not work as ít is a different one for UEFI.

    Regards,
    Jörgen​

  5. Hi,

    Does the script run in WinPE? There are known issues with the Windows 10 ADK that Powershell script fails in WinPE when PXE booted. could be the reason.

    Why not use this method to filter out the USB NIC making it re-usable for all machines. http://blogs.technet.com/b/configurationmgr/archive/2015/08/27/reusing-the-same-nic-for-multiple-pxe-initiated-deployments-in-system-center-configuration-manger-osd.aspx

    Regards,

    Jörgen

    • Like 1
  6. Hi,

    Q1 DP and PXE yes, SUP not necessary, the clients only contact it for scanning for updates, the they will pull all content from the DP

    Q2 A scondary site is just an extension of your site, it will work in the same way as it does in Site A but the data is pulled from the local DP

    Q3 You can use the same task sequence where content is accessed is controlled with boundaries and Boundary Groups.

    Q4 No UI on Secondary sites

    Q5 Not for installing a Secondary Site.

     

    A note depending on the number of clients and bandwidth you don't have to use secondary sites you can use a DP instead.

    /jörgen

  7. Hi,

    I would say that best practice is to store the Package Source files on a separate file server, DFS prefeered as you will not have to change any names in any scenario for hwupgrade or anything like that. Then you can place the data on cheaper disks with no dependency to SCCM sites or hierarchies.

    Regards,
    Jörgen

  8. Hi,

    It would have been but the Network Access Account should NEVER be local administrator on any client, the password is really easy to read during an OS Deployment if you have F8 enabled for instance, it should be a normal domain user account which you can restrict in many ways. It is only used to access content on the DP for instance. it is never used to run anything on the clients.

    So LAPS will work just fine with SCCM.

    Regards,
    Jörgen

  9. Hi,

    yes it is by design and there are two workarounds to it, either install the applications dynamically using the variable list, and populate them using a script, that way they are not in the content list of the TS and this will not occour. Or as you wrote don't deploy the TS available to all computers, have the technicians add the computer to a collection when a computer should be reimaged.

    Regards,
    Jörgen

  10. Hi,

    It is not recommended that you capture a machine that has been a member of the domain as it will leave a lot of crap in the registry and filesystem. I have never tried the steps above but I strongly recommend that you rebuild your image from scratch instead. Reusing a previous Syspreped image is not recommended either as it will also leave stuff behind.

    Regards,
    Jörgen

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