Jump to content


Rocket Man

Moderators
  • Posts

    1,009
  • Joined

  • Last visited

  • Days Won

    26

Posts posted by Rocket Man

  1. Agree with Garth - keep it simple if device limits are acceptable. Primary & DPs.

     Do the DP's need to point back to the Primary? 

    In a SCCM hierarchy all site servers have to point back(communicate if this is what you mean) to the Site Server - CAS - Primary(s)-Secondary(s)-DP(s) so a COMMs link is required in order for systems in remote locations to successfully send back CM info to site server.

    How will that be on bandwidth?

    Ultimately depends on total amount of managed systems at remote locations requiring policies from PS. DPs can be throttled if required.

    Install the MP, SUP on the DP's?

    Again depends on amount of devices at remote locations and also the link type in terms of bandwidth.

    If link is good then possibly no need for additional MP, SUP. That's a call you make yourself as you know the network.

     

     

     

  2. If you wish to rename prior to OSD within windows you could do it through WMIC command. This will allow you to remove the dashes as needed.

    The only downside is that you will need to create a extensive batch file if a large amount of PCs needs to be changed, oldname and new desired name but with excel you can do this easily and export.

    Syntax

    WMIC ComputerSystem where Name="XX-XXX-PC01" call Rename Name="AABBB-PC01"

    WMIC ComputerSystem where Name="XX-XXX-PC01" call Rename Name="BBCCC-PC01"

    WMIC ComputerSystem where Name="XX-XXX-PC01" call Rename Name="CCDDD-PC01"

     

    Create a package with batch file as above - create custom TS and copy script locally to all desired PCs from within the TS then use run command line to execute batch file locally at each PC and use an account that has domain rights to execute script in run command line. Place restart command in TS and then you could do another run command line to execute a DDR to update the CMDB with new names when the systems start backup from previous restart.

    WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000003}" /NOINTERACTIVE

    execute a delay of a 2-3 minutes so that the systems has time to update information to site server after the DDR has executed and then do another restart to update the DNS records of each systems change if you want remote control to work immediately etc... You'll need to update the collections in the console after all is finished to reflect name changes.

    Not the most convenient way of achieving this but will work - and works in windows which is a bonus.

     

     

  3. Have so far promoted 4 2K16 DCs to an existing forest and all seems fine in terms of ADDS replication/services/search etc etc..

    What is the machine above you are querying from? Is it the DC on server 2016?

    Looks like machine you are querying from is not authenticated to domain fully - or the unknown users are no longer existent or are from an old domain?

  4. SATA - max 30-35 mins - vanilla image with updates - all basic software packages including Office Pro - some business configurations\apps - NO updates -

    SSD - 20-25 mins

    4 mins ready for logon does sound somewhat unbelievable to lay down a full OS to a system - even if it was a fat image - it probably takes that to apply the OS to disk - again depends on HW and network infra to HW

    • Like 1
  5. Created ADRs for the new update servicing models, some while back now - Monthly rollup and .NET updates.

    ADR's created fine with no errors - for example

    ADR:.NetReliabilityMonthlyUpdateWin7

    ADR:Windows8.1MonthlyRollUp

     

    Have just stumbled across a possible bug - maybe this is a known bug or is isolated to this CM setup.

    When you go into the properties of the SUG it states that I must specify a valid name for software update group?

    It is due to the single . in the names of the ADRs - can anyone confirm they have similar issue?

     

     

    SUG.PNG

     

     

    Have re-edited name of SUG removing any single .'s from name and all is OK

     

    I have came across this blog that states changing the desc and name of SUGs have no bearing on the deployments and will not trigger another cycle - https://social.technet.microsoft.com/Forums/en-US/a9560993-efa6-48a8-a28a-bb0d5a472bef/sug-name-change?forum=configmanagersecurity

     

     

     

    Thanks

     

     

  6. It is not a supported function from Microsoft!

    https://support.microsoft.com/en-us/help/259670/pxe-clients-computers-do-not-start-when-you-configure-the-dynamic-host-configuration-protocol-server-to-use-options-60,-66,-67

     

    quote:

    Important: Microsoft does not support the use of these options on a DHCP server to redirect PXE clients

     

    It is after all a Microsoft product you are using, so I would imagine Microsoft would not recommend best practices otherwise!

     

    FYI: I had similar issues to what you are describing, but when options where removed as recommended from numerous blogs and IP helpers configured all worked seamlessly whether its a BIOS or UEFI boot.

     

    Also another reason as to why you should use IP helpers: https://www.windows-noob.com/forums/topic/15029-can-only-uefi-pxe-nce-no-longer-pxe-boots-afterwards/

  7. Have you specified that the laptop is to use UEFI only in the BIOS, as your TS has both BIOS and UEFI enabled? Enabling the network stack only gives you the UEFI boot options, I know the E7270's come with UEFI mode enabled by default and you have to then enable use UEFI stack to get the option, maybe 74xx's are same but you mention that you can image fine in Legacy BIOS so maybe you haven't reverted back fully to UEFI when trying? Also disable secure boot if imaging in UEFI and using Windows 7.

  8. DHCP options are not supported, use IP helpers instead which are configured on the core switches of the network.

     

     

    Right now, if I set my UEFI TS to my 64bit boot image, it breaks all my 32bit OSD

     

    You cant image an x86 machine using a x64 boot image but you can however image an x64 machine using an x86 boot file, would that be what you mean by it breaks my 32bit OSD

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