MDOP 2015 ISO INSTALL
Setup a shared folder somewhere your clients have access to and install Lenovo’s Update Retriever to get your repository all set up. You can use Lenovo’s enterprise ThinInstaller repository with SCCM, it just takes a little work.
MDOP 2015 ISO DRIVERS
You can attempt to manage the drivers in SCCM like other models but you will have a hard time getting them into importable formats since most of the lenovo driver downloads for older models are. Lenovo is a royal PITA when it comes to drivers.
Using File Explorer, navigate to the C:\Program Files\Microsoft DaRT\v8.1 folder.But no worries, to install DaRT 8.1 anyway, trick the DaRT 8.1 setup to install by doing an administrative install: msiexec /a MSDaRT81.msi
MDOP 2015 ISO WINDOWS
Note: If you still run Windows Server 2012 (non-R2) on your ConfigMgr 2012 R2 Site Server you get an “evil” error message when trying to install DaRT 8.1.
MDOP 2015 ISO SOFTWARE
One of the greatest benefits of the MDOP 2013 R2 software assurance add-on is DaRT.
Enable WinPE 5.0 remote connection (via DaRT 8.1) in ConfigMgr 2012 R2 Real time monitoring of the ConfigMgr 2012 R2 deployments in the MDT 2013 Deployment Workbench. Start a deployment, and as soon as the task sequence has run the Gather action you see the machine in the Monitoring node.Update the Distribution Points for Settings package.Using Notepad, edit the CustomSettings.ini file, and add the following entry in the end:ĮventService= Sample CustomSettings.ini file.On CM01, using File Explorer, navigate to D:\SCCM_Sources\OSD\Settings\Windows 8.1 圆4 Settings.In these steps I assume you already created a MDT 2013 Task Sequence, a MDT 2013 package, and a Settings package as part of that process. In this example my settings package for ConfigMgr 2012 has its package source path on D:\SCCM_Sources\OSD\Settings\Windows 8.1 圆4 Settings. Setup ConfigMgr 2012 R2 to use MonitoringĪfter enabling the monitoring feature, you need to configure the CustomSettings.ini file in your settings package. The console even appears to hang, but no worries, just give it some time J Note: It will take a while for the Deployment Workbench to create the monitoring database and web service. In the Monitoring tab, select the Enable monitoring for this deployment share check box, and then click OK.Right-click the new MDT Production Deployment Share and select Properties.Deployment share description: MDT Production.Deployment share path: D:\MDTProduction.Use the following settings for the New Deployment Share Wizard.On CM01, using the Deployment Workbench, right-click Deployment Shares and select New Deployment Share.In this example my site server is named CM01.
To install the web service and database used for monitoring ConfigMgr 2012 R2 you use MDT Deployment Workbench. Enable Monitoring in Deployment Workbench That way you get an easy way to remote into the machines that you are deploying (without having to specify IP address, port and ticket number for DaRT). Adding DaRT 8.1 is quite straigh forward, but it really helps if you also enable the MDT monitoring capabilities also for ConfigMgr 2012 R2 OS Deployment. When integrating MDT 2013 with ConfigMgr 2012 R2 (which you should, Capish!), and if you have access to DaRT 8.1 (MDOP 2013 R2), you can remote into WinPE when deploying the machines, great for troubleshooting. Below is a blog post I snagged from the great Johan Arwidmark.
0 kommentar(er)
