Fujitsu Software ServerView Deployment Pack for Microsoft System Center Configuration Manager ========================================================= Version 4.1.4 Date 2018-11-14 Status Released Release Notes Copyright 2018 FUJITSU LIMITED All rights reserved. Description ----------- The ServerView Deployment Pack for Microsoft System Center Configuration Manager (SCCM) is intended to enable users to configure and deploy PRIMERGY servers using Microsoft SCCM. The pack leverage's off the WinPE-based tools provided by the ServerView Scripting ToolKit, and extends the SCCM with tools and scripts. ServerView Installation Manager is required to provide up-to-date drivers and WinPE versions to integrate into SCCM. The ServerView Deployment Pack supports SCCM 2012, SCCM 2012 SP1, SCCM 2012 R2 CU1-CU4, SCCM 1515, SCCM 1602, SCCM 1606, SCCM 1610, SCCM 1702, SCCM 1706, SCCM 1710. This guide describes the tools and features provided by the ServerView Deployment Pack and how they can be employed in an MS SCCM environment for PRIMERGY servers. For more information about Microsoft System Center Configuration Manager please refer to the documentation at: http://www.microsoft.com/germany/systemcenter/sccm/default.mspx The ServerView Deployment Pack contains: - A collection of scripts to integrate the ServerView Scripting ToolKit for PRIMERGY hardware configuration within Microsoft SCCM - Tools for handling Fujitsu Technology Solution's ServerView Suite DVDs and PRIMERGY Operating System Deployment - Documentation The ServerView Deployment Pack is located on the - ServerView Suite - Management and Serviceability DVD: \start.html or - Fujitsu's support website http://support.ts.fujitsu.com/prim_supportcd/start.html In both cases follow Software Products – ServerView – Integration Solutions – ServerView Deployment Pack for Microsoft SCCM Things you need before getting started: - ServerView Suite V11.14.11 or later - ServerView Scripting ToolKit V4.0 or later. All packages are located on the ServerView IM DVD or on the support website, follow Software Products – ServerView – Deployment Tools – ServerView Scripting ToolKit Installation ------------ Preconditions: - Microsoft System Center Configuration Manager configured - ServerView Installation Manager V11.14.11 or later for WinPE Images and drivers - The ServerView Scripting ToolKit (also provided on the ServerView Suite - Management and Serviceability DVD) V4.0 or later. The ServerView Deployment Pack for Microsoft System Center Configuration Manager is distributed as ‘SVDPSCCM.msi’. The usual MSI-Installation rules apply. Supported SCCM Versions ----------------------- - Microsoft SCCM 2012 - Microsoft SCCM 2012 SP1 - Microsoft SCCM 2012 R2 (and Cumulative Update 1) Required - Microsoft SCCM 2012 R2 (and Cumulative Update 5) - Microsoft SCCM 2012 R2 SP1 - Microsoft SCCM 1511 - Microsoft SCCM 1602 - Microsoft SCCM 1606 - Microsoft SCCM 1706 - Microsoft SCCM 1710 Limitations and Caveats ----------------------- - TaskSequence Use of the generated "Fujitsu BareMetal OSD" task sequence may fail (continuous looping on Hardware set up) on SCCM 2012 R2. SCCM 2012 R2 can be repaired by installing either Cumulative Update 1 or KB2907591: http://support.microsoft.com/kb/2907591. - PostInstallPkg During testing it was found that use of the PostInstallPkg task sequence step in the generated "Fujitsu BareMetal OSD" task sequence works only on SCCM2012 R2. This is because a later version of the Microsoft Configuration Manager Client is required. - OSD (Operating System Deployment) Drivers If two drivers are available for different Operating Systems, with different binaries but the same Version number SCCM may not import the later one. Instead the first imported version will be used which may led to a blue screen when the target system reboots. Work around requires removing the earlier driver and then reinstalling the later driver. - Import of WinPE3x86 on SCCM2012 R2 CU1 is not supported but offered. WinPE3x86 is not supported by this version of SVDPSCCM. When the offered WinPE3x86 check box is selected and an import started, control immediately returns without importing the WinPE3x86 image. - PowerShell Cmdlet Get-Help -examples The Syntax displayed from Get-Help -examples does not always have the required parameter syntax. - DriverPackage removal Removal of a driver package should cause the associated drivers to be removed too. Currently this is not done because no reliable mechanism for not removing a driver that appears in more than one driverpackage has been found. - BareMetal Task Sequence profile. A Name supplied in a PropertySheet for a Task Sequence step will not appear in the generated Task Sequence. - Post Install Package removal. Importing the Post Install files from DVD causes the files that are copied to retain the read only flag which then prevents the package from being cleanly removed. These files must manually be deleted afterwards, the SCCM package is cleanly removed from SCCM.