Jump to content




kweathe

Established Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

1 Neutral

About kweathe

  • Rank
    Newbie

Contact Methods

  • Website URL
    http://247sccm.com

Profile Information

  • Gender
    Male
  • Location
    Texas
  • Interests
    System Center Suite, SharePoint, VDI, App V
  1. Chris you bring up another good point. One way to speed things up is modify when certain collections update membership. I always check Incremental and set the imaging collection to update every hour when we are doing a bulk run. You can also manually run a membership update. It's not instant but close enough in most cases. And like Rocket Man suggest you can delete the object, you are reimaging anyway. One note, clearing the PXE flag only works for required deployments. That is not an option for available since you are always presented with the deployment choices that are deployed as available to that collection group.
  2. kweathe

    KMS Not Automaticall Activating

    A great tool with KMS is the Volume Activation Management Tool or VAMT. You can remotely (through WMI) Change MAK to KMS Client Keys You can also initiate activations for both Windows and Office. Keep track of Licensing. https://technet.microsoft.com/en-us/library/ff686876.aspx
  3. I am not sure if everyone has a solid answer yet but I have working with this issue for a while. I will highlight below. You can direct boot images x86 and x64 through the use of Collections and Targeted Boot Image on the Task Sequence. With that said unknown computer support has been THE issue. CLAMB is right to separate the Unknown x86 and Unknown x64. However, once you do that you can NEVER use the combined All Unknown Collections again. UEFI has to match architecture. Traditional Bios or UEFI in legacy can use the X86 for both x86 and x64. This is not an SCCM problem or a PXE problem but a UEFI architecture change. When the machine sends a request SCCM through PXE, SCCM determines what to present based on if it's known or unknown. If it is known then it presents based on what collections the device MAC is associated with. If it is unknown and unknown computer support is enable then SCCM will present those options. Because the All Unknown Collection has both architecture types in the collection SCCM will present the boot image on the last known deployment type. Many of us attribute this as an SCCM problem. And granted MS could have done a better job by not lumping the two together but this is a fairly new issue and UEFI is still young. This is what I have done to solve the issue and it seems to be working as expected. I no longer have to swap around Task Sequences because of the SCCM last Deployment rule. Tablets and UEFI have made some interesting changes in the way we construct Collections and Target Deployment. I see this issue everywhere I go and there have not been any good articles that walk through it. I hope this helps someone. http://247sccm.com/sccm-2012-r2-pxe-with-uefi/
×