Applications, Configuration Manager 2012, Deployment, Error

App Install Failed 80004005 – SCCM OSD Standalone Media

Issue:

I created a standalone media of a fully functioning network build task sequence. A number of applications would not install from the stand alone media.

The SMSTS.log showed the following:
App install failed.
Install application action failed: ‘Office_2016_ProPlus_16.0.4266.1001_P1’. Error Code 0x80004005

No MSI log file was created, so the installer didn’t even begin.

Solution:

In the task sequence the application had the Retry this step if computer unexpectedly restarts option enabled. Disable this setting and the stand alone media worked correctly.

#DuncanToTheRescue

Advertisements
Deployment, Office 365, Windows 10

Microsoft 365 Powered Device Assessment Kit & Service Offerings Guide

In this session we will talk about how to engage your customers to deploy modern Windows and Office and keep them always up-to-date. Learn about the Microsoft 365 powered device Assessment kit based on Windows Analytics and how it can assist you to engage customers as they consider the move to, and support of, Windows 10 and Office ProPlus. We will also discuss some of the potential services opportunities related to Microsoft 365 powered device, that you can package and offer to your customers.

Products featured: Windows 10, Office 365 ProPlus

Watch a replay: https://www.microsoft.com/microsoft-365/partners/videos/assessment-kit-and-service-offerings-guide

Administration, Configuration Manager 2012, Configuration Manager 2016, Deployment, Microsoft, Office 365, OMS

WEBINAR – Simplify your Windows 10 servicing with Upgrade Readiness

Accelerate upgrades to new releases

Windows Analytics Upgrade Readiness is a free Windows Analytics service (included with Windows 10 Pro and above) that helps you upgrade to and service Windows 10, end to end. With powerful, data-driven insights and guided workflows, it allows you to adopt new releases more quickly and easily.

Join this webinar to:

  • Get a detailed walk-through and see demos of how Upgrade Readiness works.
  • Find out how Upgrade Readiness offers insight into update progress, driver issues, and feedback from end users.
  • Learn how you can use this tool to export data to commonly-used software deployment tools, including System Center Configuration Manager.

Link to view the on-demand version of the webinar for your future reference: Click here to join the webinar >

Administration, Configuration Manager 2012, Deployment

Reusing the same USB to Ethernet adapter for multiple deployments

MAC Addresses are unique identifiers of network interfaces but when reusing the same USB to Ethernet adapter for multiple deployments, your MAC Address is not unique. SCCM think that’s the same device and your device don’t receive the Task Sequence.

Beginning with SCCM 1610, you can provide a list of hardware IDs that SCCM will ignore when using PXE boot and client registration. You can now exclude the MAC address and SMBIOS GUID in the console so that same adapters can easily be reused.

  1. In the SCCM console, go to Administration / Site Configuration / Sites
  2. On the top ribbon, click Hierarchy Settings
  3. SCCM Duplicate Hardware Identifiers
  4. In the Client Approval and Conflicting Records tab
  5. In the Duplicate hardware identifiers section, click Add and enter your MAC Address or SMBIOS GUID to exclude
Active Directory, Administration, Azure, Configuration Manager 2012, Configuration Manager 2016, Deployment, EMS, Intune, Microsoft, Office 365, Security, Training & Workshop, Uncategorized, Windows 10

Microsoft Ignite – Configuration Manager What’s Next?

System Center Configuration Manager Overview and Roadmap

Learn about the latest developments in System Center Configuration Manager (ConfigMgr), watch demos, and understand what is coming next.

Windows has evolved. Simplify Windows 10 management and lower the Total Cost of Ownership (TCO) with the Microsoft Cloud. See how Enterprise Mobility + Security (EMS) and Windows 10 can be used together to ease procurement, simplify provisioning and lower TCO through modern management & security, and deliver cloud-based updates without the need for an on-premises infrastructure.

windows-10-management-ems

Administration, Deployment, EMS, Endpoint Computing Devces, Intune, Microsoft, Security, Training & Workshop

Identity-Driven UEM with Microsoft EMS

This webinar illustrates how Microsoft Enterprise Mobility + Security (EMS) provides an identity-driven unified endpoint management solution that can help you manage and secure user identities, devices, apps, and data across all of your iOS, macOS, Android, and Windows devices.

https://resources.office.com/ww-thankyou-M365PD-Identity-Driven-UEM-with-EMS-Video.html?LCID=EN-US

Azure, Conference, Configuration Manager 2012, Deployment, Intune, Microsoft, Office 365, System Center, Training & Workshop, Windows 10

Microsoft 365 Enterprise Tech Series – Enterprise Deployment & Management Technical Workshop L300

Microsoft 365 Enterprise Tech Series – Enterprise Deployment & Management Technical Workshop L300

November 30-December 1, 2017 | Auckland, New Zealand

A 2-day Training on the Complete, Intelligent, Secure Solution that Empowers Employees

What is Microsoft 365 Enterprise Tech Series?

Microsoft 365 is a complete, intelligent solution, including Office 365, Windows 10, and Enterprise Mobility + Security, that empowers everyone to be creative and work together, securely. The Enterprise Tech Series will help empower your team, safeguard your business, and simplify IT management with a single solution, purpose-built for your business

What to Expect from Training:

Understand the Microsoft 365 Vision
Dive into Modern IT Deployment
Learn about Traditional IT Transformation
Feel equipped to fully manage Microsoft 365 environments

BIOS, Configuration Manager 2012, Configuration Manager 2016, Deployment, MDT, Microsoft, UEFI, Uncategorized

Windows 10 – Switch from BIOS-to-UEFI Webinar

If you’re planning your Windows 10 migration, the switch from BIOS-to-UEFI is a hugely important piece of the puzzle.

Unless all your Windows machines are configured to UEFI, your organization cannot take advantage of the special Windows 10 security features. Microsoft’s ‘MBR2GPT’ tool still only gets you part of the way there.

This webinar was hosted live from Redmond by Microsoft MVP Jörgen Nilsson and Jim Bezdan, will ensure you know how to complete the BIOS-to-UEFI process fully, securely and automatically.

The full webinar recording can be viewed here: https://www.1e.com/on-demand-webinar/automate-bios-to-uefi-2018-edition/

Administration, BIOS, Deployment, DHCP, PXE, UEFI

DHCP Policies and Custom Vendor Classes

Many organisations still have legacy BIOS devices that do not support UEFI boot. So setup DHCP to provide both BIOS or UEFI boot files depending on what the device BIOS uses.

By using DHCP policies and custom vendor classes for the following DHCP Options:

Option 60
Option 66
Option 67

Assume that you have CM configured with a PXE enabled distribution point and a valid and configured DHCP server. You should therefore be at a configured state where you are able to PXE boot BIOS based devices.

Create Custom Vendor Classes for Use with your DHCP Policy

Think Custom Vendor Classes as Detection Method’s used to determine how devices are requesting a boot image from the DHCP server.

Open the DHCP Console and expand the IPv4 Node
Right-Click on ‘IPv4 Node’ and select ‘Define Vendor Classes’
Click ‘Add’
Create the UEFI 64-Bit Vendor class first by entering the following information
Enter the following information for the respective fields:
DisplayName: PXEClient (UEFI x64)
Description: PXEClient:Arch:00007
ASCII: PXEClient:Arch:00007
Click ‘OK’
Click ‘Add’
DisplayName: PXEClient (UEFI x86)
Description: PXEClient:Arch:00006
ASCII: PXEClient:Arch:00006
Click ‘OK’
Click ‘Add’
DisplayName: PXEClient (BIOS x86 & x64)
Description: PXEClient:Arch:00000
ASCII: PXEClient:Arch:00000
Click ‘OK’

Creating Custom DHCP Policies

UEFI 64-Bit DHCP Policy

Right-Click ‘Policies’ and click ‘New Policy’
Give the policy a friendly name that coincides with the your vendor class naming scheme:
PolicyName: PXEClient (UEFI x64)
Description: Delivers the correct bootfile for (UEFI x64)
Click ‘Next’
On the ‘Configure Conditions for the policy’ page click ‘add’
Select the ‘Value’ drop-down box and select the PXEClient (UEFI x64) vendor class that you created in previous steps
Ensure that you check the box ‘Append wildcard(*)’
Select ‘Add’
Select ‘Ok’
Click ‘Next’
If you want the policy to affect only a specific range within your scope configure it, otherwise select no and click ‘next’
On the Configure settings for the policy page ensure that ‘DHCP Standard Options’ is selected from the drop down box
Configure the following scope options:
060: PXEClient
066: IP Address of the SCCM or WDS Service
067: smsboot\x64\wdsmgfw.efi
Cick ‘Next’
On the Summary page click ‘Finish’

BIOS 32-Bit & 64-Bit DHCP Policy

Right-Click ‘Policies’ and click ‘New Policy’
Give the policy a friendly name that coincides with the your vendor class naming scheme:
PolicyName: PXEClient (BIOS x86 & x64)
Description: Delivers the correct bootfile for BIOS machines
Click ‘Next’
On the ‘Configure Conditions for the policy’ page click ‘add’
Select the ‘Value’ drop-down box and select the PXEClient (BIOS x86 & x64) vendor class that you created in previous steps
Ensure that you check the box ‘Append wildcard(*)’
Select ‘Add’
Select ‘Ok’
Click ‘Next’
If you want the policy to affect only a specific range within your scope configure it, otherwise select no and click ‘next’
On the Configure settings for the policy page ensure that ‘DHCP Standard Options’ is selected from the drop down box
Configure the following scope options:
060: PXEClient
066: IP Address of the SCCM or WDS Service
067: smsboot\x64\wdsnbp.com
Cick ‘Next’
On the Summary page click ‘Finish’

UEFI 32-Bit DHCP Policy

Right-Click ‘Policies’ and click ‘New Policy’
Give the policy a friendly name that coincides with the your vendor class naming scheme:
PolicyName: PXEClient (UEFI x86)
Description: Delivers the correct bootfile for (UEFI x86) machines
Click ‘Next’
On the ‘Configure Conditions for the policy’ page click ‘add’
Select the ‘Value’ drop-down box and select the PXEClient (UEFI x86) vendor class that you created in previous steps
Ensure that you check the box ‘Append wildcard(*)’
Select ‘Add’
Select ‘Ok’
Click ‘Next’
If you want the policy to affect only a specific range within your scope configure it, otherwise select no and click ‘next’
On the Configure settings for the policy page ensure that ‘DHCP Standard Options’ is selected from the drop down box
Configure the following scope options:
060: PXEClient
066: IP Address of the SCCM or WDS Service
067: smsboot\x86\wdsmgfw.efi
Cick ‘Next’
On the Summary page click ‘Finish’

Remove Default PXE Options

Ensure that you have removed the 067, 066, 060 options from the default scope options to ensure that the Policies take precedence otherwise you will end up with conflict

As long as you have configured everything correctly you should now have the ability to boot machines from  BIOS or UEFI.

Administration, Azure, Deployment, EMS, Microsoft, Office 365, Windows 10

Windows AutoPilot Deployment

Microsoft has announced that Windows AutoPilot Deployment – a new cloud service that enables IT professionals and partners to customize the Windows 10 out of box setup experience. It used cloud configuration, delivering a self-service deployment experience with new Windows 10 Pro devices. It is now available through CSP.https://blogs.windows.com/business/2017/06/29/delivering-modern-promise-windows-10/#7Y0FQE61FUq42yKb.97

For Windows AutoPilot Deployment feature overviews and demos please see below: