Add or remove local user in SCCM 2012 OSD Task Sequence

Sometimes it is necessary to add of remove a local user to your Windows image (like notebooks which must be used at external locations). You can create an image for SCCM with local users, but then you have another image with a different configuration. I think it’s cool everything can be managed with just one image, so here is a small tip to add an user from the task sequence.

The command net user can be used to add a local user, or delete it:
Add user
net user username password /add

Delete user
net user username /delete

Look at http://support.microsoft.com/kb/251394 for the right parameters.

I want to delete a user account which was created during a manual image built.
net user username /delete

Next thing is to add the command line to the task sequence:
1. Edit the Task Sequence
2. Choose Add, General, Run Command Line
Note:
The user can’t be added as all steps in the Install Operating System group are executed in WinPE.
The creation of the user to the end of the TS, after setting up the SCCM client and after restoring the user data.
ScreenHunter_264 Dec. 10 11.21
3. Type or paste the command in the Command line: box

 

CCMsetup.exe will not install: Failed to access source file (3)

Issue
Today we bumped into an issue installing the SCCM client manually. The error in the C:\Windows\CCMSetup\ccmsetup.log stated “Failed to access source file (3). Waiting for retry.”

<![LOG[Downloading file C:\Windows\System32\drivers\sccm\SCCM Client\ccmsetup.exe]LOG]!><time=”10:40:53.549-120″ date=”05-31-2013″ component=”ccmsetup” context=”” type=”1″ thread=”3780″ file=”ccmsetup.cpp:5569″>
<![LOG[Downloading C:\Windows\System32\drivers\sccm\SCCM Client\ccmsetup.exe to C:\Windows\ccmsetup\ccmsetup.exe]LOG]!><time=”10:40:53.549-120″ date=”05-31-2013″ component=”ccmsetup” context=”” type=”1″ thread=”3780″ file=”ccmsetup.cpp:5653″>
<![LOG[Failed to access source file (3). Waiting for retry…]LOG]!><time=”10:40:53.549-120″ date=”05-31-2013″ component=”ccmsetup” context=”” type=”2″ thread=”3780″ file=”ccmsetup.cpp:5665″>
<![LOG[Next retry in 10 minute(s)…]LOG]!><time=”10:40:53.549-120″ date=”05-31-2013″ component=”ccmsetup” context=”” type=”0″ thread=”3780″ file=”ccmsetup.cpp:8498″>

Cause and solution
After some investigation we discovered that the customer copied the SCCM setup folder in the C:\Windows\System32 folder and was running the setup from there. This is because of security prohibited. After this we moved the folder to C:\temp and the setup ran fine.

Step by Step: Installing SCCM 2012 SP1 on Windows Server 2012 and SQL 2012 SP1

Well, after some testing with SCCM 2012 SP1 I decided to reinstall everything in my lab to the latest software. So Windows 2012, SQL 2012 RTM and of course System Center Configuration Manager 2012 SP1.

In this blog I used my laptop:
-Intel(R) i5-2410M CPU @ 2.30GHz, 2 Core(s)
-8 Gb of internal memory
-Two SSD disk (C:\ for OS and D:\ for Hyper-V)

Lab setup:
Domain Controller: Windows 2012 Enterprise; DC, DNS and certificate server
SCCM 2012; Windows 2012 Enterprise, SQL 2012 Enterprise, IIS and SCCM components

1. SQL 2012 installation
ConfigMgr 2012 SP1 Beta supports SQL 2012 RTM with a minimum of CU 2. ConfigMgr has very strict SQL collation requirement, pretty much across the entire System Center range, essentially only SQL_Latin1_General_CP1_CI_AS collation is supported.
This has to be selected during installation if you are running a non-USA regional\system OS.

– Login as the SQL admin on the SQL Server
– Launch the SQL 2012 RTM installer
Select Installation on the left navigation pane
Select New SQL Server stand-alone installation or add features to an existing installation
– Ok, Next,
and choose Accept the license terms, Next
We will open the Firewall later, so skip the warning
– Choose Next
– Select SQL Server Feature Installation


Select the following
– Database Engine Services
– Reporting Services – Native
– Management Tools – Basic
– Management Tools – Complete
Because I’m in a test environment I didn’t change the path’s. In production it’s recommended to choose alternative path’s
Next, Next

– Choose the default Default instance, and change the path’s if necessary and choose Next, Next
By default each of the services will be configured using a service-specific user account, we used NT AUTHORITY\SYSTEM

Do this for the SQL Server Agent, the SQL Server Database Engine and the SQL Server Reporting Services services
– Click Account Name, Browse, Browse locally for SYSTEM and accept
– Set the services Start-up Type to automatic
Select the Collation tab
– Double check
If SQL_Latin1_General_CP1_CI_AS is shown, otherwise Customize this, Next
Add the current user and a domain user at this point. I add the SQL admin and the local administrator, Next
– Select Install and configure, Next
Set Send Windows and SQL Server Error Reports to Microsoft, choose Next, Next
Alrighty then SQL is Ready, lets rock.

– Next we will run SQL 2012 SP1 (SCCM 2012 requires minimal CU2 to have an successful install)
Download link SP1 http://www.microsoft.com/en-us/download/details.aspx?id=35575
Download link CU1 http://support.microsoft.com/kb/2765331

Note If you do not install CU2 (or SP1) you’ll receive SQL Server Version Error in the Perquisites.

The Advanced logging says that the SQL server Version is not supported. So patch you’re SQL Server.

Make the nessesary Firewall Exeptions for SCCM;
– Open the settings, Control Panel, System and Security, Windows Firewall
– Choose Advanced Settings, Inbound rules
– Create a new Rule called SQL Ports,
– On Rule Type, Choose Ports, Next
– On theTCP tab 4022, 1433 and click Next
ScreenHunter_191 Jan. 25 10.08
– Choose allow the connection, Next
– On profile choose all, Next
Fill in a name (we used SQL Ports)


2. Installing the SCCM 2012 Perquisites
Open Server Manager
– Select Add Roles and features, click Next
– Choose Role Based or Feature based installation
– Select the local server, Next
Open Web Server (IIS) and ADD select the following features
Common
HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection

Application
Development
ASP.NET
.NET Extensibility
ASP
ISAPI Extensions
ISAPI Filters

Health and Diagnostics
HTTP logging
Logging tools
Request Monitor
Tracing

Security
Basic Authentication
Windows Authentication
URL Authorization
Request Filtering
IP and Domain Restrictions

Performance
Static Content
Compression

Management Tools IIS Management Console IIS Management Scripts and Tools Management Service IIS 6 Management Compatibilty IIS 6 Metabase Compatibility IIS 6 WMI Compatibility IIS 6 Scripting Tools IIS 6 Management Console
– Select Windows Server Update Services, Add features
– Select Windows Deployment Services, Add Features

– Choose Background Intelligent Transfer Service (BITS), Add features
– Choose Remote Differential Compression
– Telnet Client (not necessary but it’s useful), Next
– On the WSUS section choose next.
– On the Role Services choose WSUS Services and Database, Next
– Choose Store updates and choose a location (This is a testlab, in production it is not recommended to save these files to the C:\ drive), Next

– Type the SQL Server name and choose Check connection

– Next, Next,
– Choose Deployment Server and Transport Server
– Next, Install

3. Install the WADK (Windows Assessment and Deployment Kit)
In Windows 2012 you no longer use WAIK, we’re now on WADK for Windows 8.
– Go to http://go.microsoft.com/fwlink/?LinkID=252874 and download the ADK Setup.
– Run the ADKSetup.exe as an administrator

– I left the path’s default and choose Next
– Choose if you want to join CEIP and choose Next
Accept the Licence Agreement and choose Accept
– Check Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tools (USMT)

– Choose Next and install the Software

3. Next step is to install SCCM 2012 SP1 Beta
Ok, we are now ready to install ConfigMgr 2012 SP 1 Beta
– Launch the spash.HTA from the installation media

– First check the server is ready before we get any further into the installer Select Assess server readiness

Some minor issues but no show stoppers so lets continue
– Go back to the Splash.hta screen and click Install, Choose Next
– Because we are on one demo server we choose Install a Configuration Manager Primary Site and check the Use typical installation… Choose Next.

– Choose yes and I Agree, Next
– Accept all the licence therms and choose next

– Download the files to a folder you choose and click Next

-Choose a site code, Site name and installation folder for SCCM 2012 SP1, Next

– Hit next a couple of times and then choose Begin Install

That’s it, we are now up and running.

SP1 brings a lot of nice new stuff like the cross-platform clients, Azure Cloud DP, mobile device management through Microsoft Exchange ActiveSync amongst others.
Check out what’s new in SP1 here for a list of fun things to play around with and get to know in preparation for the actual SP1 release, as well as the release notes detailing what is knowing to be in a broken state during the Beta. You can also provide feedback to Microsoft for anything quirky that you may find during the evaluation.

Have Fun!

Office 2013 deployment with SCCM 2012 SP1 (Beta)

Just another tutorial on how to deploy Office 2013 using Configuration Manager 2012 SP1.

Extracting the Office installation and customizing the installation
First I started to get the Office 2013 software from the MSDN site and extracted it into my demo lab share file.
1. In my case it was on \\demo-sccm01\Sources\Software\Office\Office 2013 Pro NL x64.


Second step is to customize the Office 2013 installation using the “Office Customization Tool”;
2. Go to a DOS prompt, go the Office 2013 folder and run setup.exe /admin
If the setup /admin runs well go to step 3, otherwise go to step 2.1
2.1 – Optional
If you run the setup.exe /admin you can receive the following error:

Files necessary to run the Office Customization Tool were not found. Run Setup from the installation point of a qualifying product.

To solve this issue, click HERE and extract the admin files in the root of the Office 2013 directory.

3. Choose Ok to create a new Setup Customization file

4. On Default File Types, I selected Office Open XML formats

5. On the Licensing and user interface check the I Accept terms and choose Display Level – none

6. Customize the further installation of Office 2013 to you’re needs.
7. Save it where the setup.exe is located. I used the name Office2013NLD_x64_Custom.msp

Next step is do deploy Office 2013 to the SCCM 2012 SP1 environment
1. Open the Configuration Manager 2012 console, Software Library, Application Management, right-click Applications
2. Create an folder named Office and a subfolder called Office 2013
3. Right Click Create application

4. Browse to proplusww.msi (location where you extract the Office, subfolder proplusrww) and click Next
5. On view imported information, click next
6. On the General information, make adjustments/notes and click next

7. Summary, click Next and choose Close
8. Select the Microsoft Professional Plus 2013 application, and select the Deployment Type tab, click Properties
9. In the Deployment Type properties, of the Microsoft Professional Plus 2013 application, go to content tab and change the Content location from “\\demo-sccm01\Sources\Software\Office\Office 2013 Pro NL x64\proplusr.ww” to “\\demo-sccm01\Sources\Software\Office\Office 2013 Pro NL x64”
10. Go to programs tab, Installation program, type setup.exe /adminfile Office2013NLD_x64_Custom.msp

11. If necessary you can go to the requirements section and add requirements like
– 1 gigahertz (Ghz) or faster
– 1 gigabyte (GB) RAM (32 bit);
– 2 gigabytes (GB) RAM (64 bit)

12. Select the Microsoft Office Professional Plus 2013 x64 – NLD, change to Home tab and click Properties

13. Select “Allow this application to be installed form the install application task sequence action without being deployed”; this is necessary if you want to use it during the Operating System Deployment.

14. Select the Microsoft Professional Plus 2013 application and click Distribute Content

15. On the General, Click Next
16. On Content, click Next
17. On Content Destination, add the Distribution Point and click Next
18. Summary, click Next and choose Close
19. Right click on the Office App and choose Deploy, select All systems as collection (because we use it as an OSD deployment.

20. Just click next until completion, if you want to make adjustments it’s possible.
21. On the client force the machine policy retrieval

22. Open the Software Center, select Microsoft Professional Plus 2013 x64 NLD and click Install and the installation will start. After a minute of ten the installation is completed.
23. To check the deployment on the server, open the ConfigMgr console, go to monitoring, Deployments.
24. Select Microsoft Professional Plus 2013 and confirm the completion statistics