.:: (MVP) Raphael ::. : beta, 2012

[Project] - CM12 Automation RC is out!

Raphael — Thu, 10 Jan 2013 13:19:38 GMT

Hi All,

i've been busy working on the RC release of CM12Automation (http://cm12automation.codeplex.com/) and today i'm happy to say that it has been released...

the codeplex page is being updated and also, i'm uploading videos on youtube. I'll update this page once everyting is there...

hope you'll enjoy using it as much as i'm enjoying creating it.

[Project] - CM12 Automation - RC is coming

Raphael — Tue, 11 Dec 2012 11:45:07 GMT

Hi All,

This project is really going somewhere, i received lots of inputs, including lots of Microsoft people, what is really great...

Anyway..i'm finishing the RC version (final testings) and i hope i'll be able to publish it before christmas...

at the moment, these are the main changes:
1- fixed bugs (many of them)
2- created ImportReports.ps1 and created few reports (at the moment 8 reports) **if you have any report that you'd like to see, let me know
3- Removed the folder structure from the installation and created CreateProjectStructure.ps1 file and changed it
4- Changed sql folder data/logs location and memory calculation (now it also sets the mim memory)
5- BuildMedia has been upgraded
6- created universion group for exchange connector
7- added system health validator installation point, creation of IP range for the DP ip address

i'll keep you posted, but if you want to download the beta version, go to http://cm12automation.codeplex.com/

Which one is the right method to deploy apps during OS Deployment?

Raphael — Thu, 18 Oct 2012 13:35:53 GMT

Hi All,

Many times I’m asked: How should I deploy this app: Add it to the base image, during the OS Deployment (as application) or after (sw deployment via computer collections/user)

This is a trick question and my answer is always couple of questions:

1- Size of the application
2- How often it changes?
3- who uses it?
4- How often you rebuild your base image?

Anyway…as you now have an idea, let’s get the office application but let’s ask the following questions:

1- Which deployment method will use less bandwidth?
2- Which deployment method will be faster?

To answer your questions, I created 2 base images, 1 with office and another without office. The size of the base image with office is 4.03GB (4,226,404KB) and without office is 2.82GB (2,966,625KB)

Now, time of the tests:
1- Deploy OS (Windows 8) via TS and Deploy Office via Software Distribution
Result: 27 minutes, 29 seconds and used 3.93GB

2- Deploy OS (Windows 8) and Office via TS (Office is deployed as application and not part of the base image)

Result: 24 minutes, 30 seconds and used 3.93GB

3- Deploy OS (Windows 8) and Office via TS (Office is part of the base image).

Result: 27 minutes, 01 seconds and used 4.36GB

As you can see, method 2 seems to be the fastest and used less bandwidth and the method 3 is using a lot more network badwidth

Now, let’s imagine couple of applications:
1- Office: Office is a large application and, often, you deploy it to all computers (except servers). The application doesn’t change often (and you can use software updates to deploy any update). For service packs, it is released once every few months. In my opinion it is a good example of application that you could add to the base image
2- Flash: Small application, change almost every week, everyone uses. It is not a good example, this is because every time you deploy the software, you need to update it. And updating flash is not only adding couple of registry changes/file changes, it is a complete new set of files (well, flash has only couple of files anyway)
3- Line of business app: App that is deployed to a few people only, maybe changes maybe not. This is an app that I normally do not put on the base, except if you want to manage couple of base images
4- Anti-virus: I normally against putting the AV into the base image, this is because it changes a lot and I prefer have no anti-virus instead of having an anti-virus that does not do anything…but this is my opinion

My recommendations:
1- Put in the base image only applications that doesn’t change or change only couple of times per year
2- Put only large applications. Applications with less than 100MB I do not see the point (my opinion)
3- Do not add AV to the base image (my opinion)
4- Update your base image couple of times per year to add the latest updates to it and same time when performing the OS Deployment…

But why would I add any software on my base image if it is slower and use more data and I’ll need to recreate the base image couple of times a year?!?!?!?!

Before I answer that, you need be aware that there is no network issue on my lab and there is no user intervention, it means, everything works as expected.

As I only used 1 application, imagine that you need add more applications…you may have many reboots, it is more data, etc…

Now, answer your question: You need to test in your environment with your applications to discover which method will be faster and use less bandwidth and only after this you’ll be able to perform the right choice.

Monitoring Bandwidth Transfer

Raphael — Tue, 16 Oct 2012 12:22:45 GMT

Hi All,

i'm doing some tests and i'd like to monitor the network bandwidth to confirm the amount of data transfered from the server to the client (and vice versa) during many actions, like OS Deployment, SW Deployment, etc...

i was looking over the net (and asked help from MVP friends), but unfortunatelly, all solutions i had was not as easy as i wanted...until the NetWorx (http://www.softperfect.com/products/networx/) this is a free and simple Bandwidth Monitoring and Usage Reporting.

note: I installed it on my on my lab because i only have 1 DC, 1 SCCM Server and 1 client, nothing else to interfere as it doesnt have a way to filter the source/destination

anyway...as soon as you dowload it, it is time to install and configure. I installed it on my SCCM Server..and it is really easy, almost next, next finish.. :)

Now it was time to start the software (if it is not started already), easy, go to start menu, Programs, NetWorx and start the NetWorx...

On the task bar (notification icons), you'll see a new icon there, just right click and select speet meter

on the speed meter, you have 2 main buttons (start and reset) as well as a timer..

on my lab, i started it and swtiched on a "blank" vm to perform the PXE boot and stopped when it downloaded all pxe stuff and was on the PXE Main screen (that one we're you can type the password)

as you can see, it took 01 minute and 57 seconds and used 215MB (8.84 Received and 207 sent). Remember, as i cannot filter, this values also contain a bit of network from/to Domain controller

[Project] - CM12 Automation - beta release

Raphael — Fri, 05 Oct 2012 12:00:22 GMT

Hi All,

today i'm proud to announce the release of the CM12 Automation beta...

The download can be found at http://cm12automation.codeplex.com/releases/view/95777

and for more information on how to use it, look at this post: http://wmug.co.uk/wmug/b/dotraphael/archive/2012/09/28/project-cm12-automation-beta-is-coming.aspx

[Project] - CM12 Automation - beta is coming

Raphael — Fri, 28 Sep 2012 10:32:47 GMT

Hi All,

I'm really loving doing this project..and it is almost in a beta stage...there are lots of things to do still and i'd love your imput, even for bugs..(send it to me to raphael AT rflsystems.co.uk)

Anyway...the webpage of the project is http://cm12automation.codeplex.com/ and the beta files will be there soon ((i'm finishing lots of tests)

the 1st powershell script you need to know is the BuildMediaFolder.ps1

as the name says, it will build a folder with all files you need to have...there are files it will download from the internet (if you say to download) or copy from a folder (that you'll tell the folder) and other files (ie ConfigMgr 2012 SP1, SQL Server 2008 R2 RTM) that it cannot download from the next and expect you to have somewhere

if you use proxy authentication, dont worry..it will ask your username/password to connect to the net as well :)

the 2nd script is PrepareActiveDirectory.ps1

as the name says, it will prepare the active directory, create OU's, computer accounts for the SCCM Servers (if it does not exist), groups, etc..and depending on the option you selected, it will perform the schema extensions...

yes, if you have a single domain you'll need run this twice, but if you're not the guy with rights to perform the extension, you can give them the file

the 3rd script is Prerequisites.ps1

this will install all requirements for the site, sql, etc...you can use it in 1 machine or in multiple machines, like, installing the DP/MP on a remote machine, you don't need to select this option on the site server...

as part of the process, it will install the minimum requirement for the role that you'll use...

things it will do:
install and configure CMTrace
Create c:\NO_SMS_ON_Drive .sms
Create d:\NO_SMS_ON_Drive .sms (if needed, basically, if you install a site)
create sql server firewall extensions
disable firewall
add the sccm servers group and sccm admins group as local admin
install .NET Framework 4
install IIS, bits, etc..
install sql 2008 r2 + sp2 or sql express
configure the number of sql files and max memory
if you're preparing for sql server reporting services, it will also configure the execution account and backup the encryption key
install wsus 3.0 sp2 and hotfixes
install ADK
install configmgr toolkit
install powershell 3

the 4th script is the InstallSCCMSite.ps1...

this is the main script as it will install the site, it will ask questions about the site, like, type (Central, Primary Std, Primary Child), sdk server, etc...

what i like most of this are:
1- install and integrate MDT
2- validate the installation (of course, basic validation)
3- automatically add the group you create to a full admin
4- change the logs size to 10MB (yes, it may be too much, but i'm using it on my lab)
5- enable tasks "Rebuild Indexes and Backup SMS Site Server"
6- enable tasks "Delete obsolete client discovery data", "delete inactive client discovery data"
7- disable task "evaluate provisioned AMT computer certificates"
8- automatically add a client push and network access account
9- create cm12 desktop icon and configure the launch of sql reporting builder 3
10- configure the database initial size and number of files
11- create boundary and boundary group
12- enable discovery(***)
13- create device and user folders and collections
14- extend hw inventory to collect extra data (used by the script), create a client settings to collect this extra data and also deploy to the sccm collections created

and the 5th script is SiteRolesInstallation.ps1
this will install all site roles that you want, but at the moment, it only install:
1- cm12 console (i know, it is not a site server :))
2- asset intelligence sync point
3- fallback
4- management point
5- dp (and also create a dpgroup)
6- smp
7- sup
8- application catalog website and webservice point
9- endpoint protection (and create ADR)

few points:
1- script expect to find at least 2 partitions and in many cases 3 (ie c, d and e)
2- all logs are in cmtrace format :):):)
3- ***there is a bug with the discovery, try avoiding using it if possible
4- Creating Secondary site may happen later
5- script only install if needed (ie: it will not install IIS if you don't select anything that uses IIS)
6- you can either run the script without parameters and it will ask you question or you can pass parameters and it will do almost everything in a automated way...

hope you're as excited as me about this project

Deploying Windows 8 Apps

Raphael — Thu, 20 Sep 2012 10:57:00 GMT

Hi All,

another step-by-step, now on deploying windows 8 apps...

1st of all, create your app (you can follow my post on how to do it here)

Now, on CM console, we need to change the powershell execution policy, to do this, change the default client settings -> computer agent

Next step is to create the application, to do this, import a new app

Distribute the content

Create the deployment

Now the fun begin, On the client, change the Allow all trusted apps to install group policy settings (gpedit.msc) (Computer Configuration -> Administrative Tools -> Windows Components -> App Package Deployment)
**Note: I used gpedit.msc because I was only playing with 1 client and on any environment with more than 1 machine you should use GPO

Import certificate (again, on a corporate environment, use GPO to do this)

Now it is time to refresh the machine policy

When it is done, open the software center and install the application

Note that after the installation a new icon appears on the windows 8 menu

To monitor the deployment, use the deployments under monitoring on cm12 console

ConfigMgr 2012 SP1 Beta & Linux Client

Raphael — Tue, 18 Sep 2012 08:50:00 GMT

Hi All,

over the past few days i was playing with SCCM 2012 SP1 Beta and Linux...and i have to say that there are few bugs (i'll see bellow), but it works quite well...

anyway...before you start, you need a Linux box...I'm using Suse Enterprise Server 11. I downloaded it from https://www.suse.com/ and installed it....i used the default settings and after the installation, checked the network was working fine (i had a couple of problems with vmware 9 network not being able to ping the dns properly...) i added the machine to the domain. as far as i know it is not required, but i wanted to see how easy it was...and it was easy...

2nd..you need to download the linux client, and you can get the .exe from http://www.microsoft.com/en-us/download/details.aspx?id=34609

next step is to extract the file you just download

after this, copy all files to the linux server. I copied them to CM12Client (note: wihtout spaces. this is because i tried before with spaces and it did not work) and as root (i used sudo) use the command ./install (all switches you can find here http://technet.microsoft.com/en-us/library/jj573939.aspx). as you can see, i used -mp for the Management Point, -sitecode for the Sitecode, -fsp for the fallback status point and the name of the taf file

after the installation, if you open the "windows explorer" equivalent, navigage to /opt/microsoft/configmgr

because of a but at this moment, all new linux client will be always not approved...to see this, add a column approved and approve them

after this, stop the client (a list of the switches and location you can find http://technet.microsoft.com/en-us/library/jj573937.aspx. note that for Suse 11, you'll be using /opt/microsoft/configmgr/bin/ccmexec -s)

delete the cookie file using rm /opt/microsoft/configmgr/root/ccm/policy/servercookies.xml

start the client (for Suse 11, you'll be using /opt/microsoft/configmgr/bin/ccmexec -d)

perform the policy refresh (for Suse 11, you'll be using /opt/microsoft/configmgr/bin/ccmexec -rs policy)

and as soon as it finishes, request the hardware inventory (for Suse 11, you'll be using /opt/microsoft/configmgr/bin/ccmexec -rs hinv)

but keep in mind,Always monitor log file. as we don't have cmtrace you can use tail -f /var/opt/Microsoft/scxcm.log (**Thanks to Rob Marshall for this tip)

the logs are created in 2 different places (unfortunatelly the documentation has the wrong place at this moment)

on suse 11, the scxcm.log is located on /var/opt/microsoft

and the scxcmprovider.log is located on /varopt/microsoft/nanowbem instead /var/opt/microsoft/nanowbem

Couple of extra links:

http://technet.microsoft.com/en-us/library/jj573940.aspx

http://technet.microsoft.com/en-us/library/jj573941.aspx

http://technet.microsoft.com/en-us/library/jj573945.aspx

Office 2013 (Part 2)

Raphael — Fri, 14 Sep 2012 10:00:03 GMT

Hi All,

this is the part 2 on deploying office 2013 with SCCM 2012 SP1 Beta. Part 1 is available here

1. Now, open the CM12 console, go to Software Library -> Application Management and Applications

2. Click Create application

3. On Location, browse to proplusww.msi (where you extract the Office, subfolder proplus.ww)

4. Clique next

5. On view imported information, click next

6. General information, click next

7. Summary, click Next

8. Completion, click Close

9. Select the Microsoft Professional Plus 2013, select the Deployment Type and click Properties on the ribbon

10. On Microsoft Professional Plus 2013 – Windows Installer (Native) Properties, go to content tab and change the Content location from “Office 2013\proplus.ww” to “Office 13”

11. Go to programs tab and Installation program, type setup.exe /adminfile Of2013Custom.msp

12. Go to requirements tab, and add the requirements. In this example, 1GB of RAM, 2GB of free disk space and Win7/Win8 x64 bits and click OK

13. Select the Microsoft Professional Plus 2012, change to Home tab and click Properties

14. Select “Allow this application to be installed form the install application task sequence action without being deployed” if you want to use it during OSD (we will!!!) and click OK

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

16. On General, Click Next

17. On Content, click Next

18. On Content Destination, add the DP and click Next

19. Summary, click Next

20. Completion, click Close

21. On the summary page, confirm that the content status show success

22. Click on Deploy and select All systems as collection

23. On Content, click next

24. On Deployment Settings, click Next

25. On Scheduling, click next

26. On User experience, click next

27. On Alerts, click next

28. On Summary, click Next

29. On Completion, click Next

30. On the client force the machine policy retrieval

31. Open the Software Center, select Microsoft Professional Plus 2013 and click Install

32. The Download and installation will start

33. After few minutes, the installation is completed

34. And the new software appears on the start menu

35. Open the CM12 Server, CM12 console and navigate to Monitoring -> Deployments

36. Select Microsoft Professional Plus 2013 and confirm the completion statistics (you may need also run the summarization)

37. Click View status under completion statistics for more information

Office 2013 (Part 1)

Raphael — Thu, 13 Sep 2012 08:49:06 GMT

Hi All,

another step-by-step, but this time is how to deploy office 2013 using CM12.

This is part 1 of 2. In this post, we'll prepare the installation files.

1st, you need to download the office 2013 from the net. I downloaded it from the MSDN website and the file name is en_office_professional_plus_2013_preview_x64_916516.exe

1. Extract the source files with the following command en_office_professional_plus_2013_preview_x64_916516.exe /extract:”<PATH>”

2. When the extraction is completed, you’ll get the Files extracted successfully message

3. Use setup /admin to open the Microsoft Office Customization Tool

4. Click Ok to Create a new Setup Customization file

5. On Default File Types, select the option you want. I selected Office Open XML formats

6. Now, navigate to licensing and user interface and check I accept the terms in the license agreement and display level select none

7. If your using KMS, leave use KMS client key, otherwise, select Enter another product key and enter it on Product Key

8. Go to Set feature installation states to configure the software you want to install. I left only Excel, PowerPoint, Office Shared Features, Office Tools and Word

9. Save it where the setup.exe is located. I used the name Of2013Custom.msp

10. Close the Microsoft Office Customization Tool and when requested, click Yes to close

11. If you go to windows explorer, you should see the file you just created

Windows 8

Raphael — Wed, 12 Sep 2012 11:22:12 GMT

Hi All,

another step-by-step, but this time is deploying Windows 8 (I'm using Enterprise x64) with SCCM 2012 SP1 Beta.

To Start, copy the Windows 8 DVD file to a place where the Server can access and share the folder. I'm using D:\Source$\Windows 8 Enterprise x64 and the share is Source$. I'm using vmware workstation 9, and i don't need to worry about drivers at this point in time :)

it is also expected that you have enabled PXE on DP and enabled support for unknown computers...

ok..it is time to start

1. Open CM12 console and navigate to Software Library->Operating Systems->Boot Images

2. Select the Boot image (x64) and click properties

3. Go to datasource tab and make sure “Deploy this boot image from the pxe-enabled distribution point” is selected

4. Back to the console, click distribute content

5. On General, click next

6. On Content Destination, select the Distribution Point and click next

7. On summary, click next

8. On completion, click close

9. On the summary page, confirm that the content status show success

10. Repeat the process for the Boot image (x86)
11. navigate to Software Library->Operating Systems->Operating System Images

12. Click Add Operating System Image

13. On Data source, navigate to install.wim file and click Next

14. On General page, click next

15. On Summary, click Next

16. On Completion, click Close

17. Select the Windows 8 Enterprise and click Distribute Content

18. On General, click Next

19. On Content Destination, add the DP and click Next

20. On Summary, click Next

21. On Completion, click Close

22. On the summary page, confirm that the content status show success

23. navigate to Software Library->Operating Systems->Task Sequences

24. Click Create Task sequence

25. On Create new task sequence, click Next

26. On Task sequence Information, add a name and select the boot image. On my case, I selected the x64 because the Windows 8 is x64

27. On Install Windows, select the package we imported previously, remove configure task sequence for use with bitlocker and click next

28. On Configure network, configure the network. In this example we’ll be adding this machine to a domain

29. On Install the Configuration Manager Client, click Next

30. On Configure state migration, you can remove all as this will not apply in this case

31. Include software updates, click next

32. Install applications, add all application you want click Next

33. Confirm the settings, click next

34. Completion, click close

35. Select the Deploy Windows 8 task sequence and select Deploy

36. On Specify general information for this deployment, select collection all unknown computers and click next

37. On Deployment Settings, select Make available to the following: Only media and PXE and click next

38. On Scheduling, click next

39. On User experience, click next

40. On alerts, click next

41. On distribution point, click next

42. On summary, click next

43. On completion, click close

44. Boot the computer on windows pe and when requested, press F12

45. On the welcome to the task sequence wizard, click next

46. On Select a task sequence to run, click Next

47. Task sequence will start

48. After couple of reboots, you’ll get this:

49. navigate to Assets and Compliance->Devices and you’ll see the new machine

Different from previous versions, using the default wim file won't install windows to the D drive, it will install on C drive...

Install App-V Sequencer

Raphael — Tue, 11 Sep 2012 08:33:00 GMT

Hi All,

this is another step-by-step on how to run Java virtualized app's with SCCM 2012 SP1

I already downloaded and installed SCCM 2012 SP1 Beta (More info about it here)

Before you start, download and install the following softwares:
1- Download app-v 5 from https://connect.microsoft.com/MDOPTAP
2- Download and install .net framework 4 (http://www.microsoft.com/en-us/download/details.aspx?id=17718)
3- Download and install powershell 3 http://www.microsoft.com/en-us/download/details.aspx?id=34595
4- Download and install KB2533623 http://support.microsoft.com/kb/2533623

if you don't do this, you'll see the following messages:

Now that we have installed the requirements, lets install the sequencer. To do this, execute appv_sequencer_setup file

Click Install

Click I accept the license terms and Next

Click Install

When the setup is completed, click Close

When you open the start menu, you should see the Microsoft Applicaiton Virtualization Sequencer

next post we'll start playing with the sequencer...

[Project] - CM12 Automation

Raphael — Fri, 31 Aug 2012 18:27:58 GMT

Hi All,

I created a project on codeplex called cm12 automation.

The goal is to automate (using powershell) all CM12 basic tasks...

at this moment, there are few scripts:
0- Functions.ps1
- used by the other scripts

1- prepareActiveDirectory.ps1
- this scripts create ad containers, groups, users and extend schema

2- prerequisites.ps1
- this install all requirements needed for the site server and site roles (ie. sql, iis, etc)

3- InstallSCCMSite.ps1
- this install cm12 (Sp1 ctp at the moment) with basic settings and validate its installation. it does not install MP or DP. You can use to install CAS, Primary Child or primary std

there are updates to allow install site servers like management point, fallback status point, etc...

the project is published here http://cm12automation.codeplex.com/

[Project] ConfigMgrRegistrationRequest

Raphael — Tue, 22 May 2012 14:01:00 GMT

Hi All,

i just published this project on CodePlex (https://configmgrregistratio.codeplex.com/). It is still in pre-beta, but worth to check it out.

Basically, this project will allow you to create Fake Clients, ideal when you need test load, reports, etc...

when you run the tool (as a local Administrator), it will
-          Open a csv file and send request to register a new client to sccm
-          Send a update client id to sccm
-          Request policy
-          Send a ddr message
-          Send hinv

To run: ConfigMgrRegistrationRequest /MPName:<MP Name/IPAddress> /FileName:"<CSV File>" /debug:true

Note that there is a file called HINVTemplate.xml with the HINV information template

the code ignores the 1^st line on the csv file as it is only information

SMSGUID

Computer Name

Domain (FQDN)

Domain (Netbios)

AD Site Name

ConfigMgr Site Code

Mac Address

IPAddress

IPSubnet

Windows OS Version

ConfigMgr Client Version

Memory

When you run, it will create certificates to communicate with the ConfigMgr infrastructure and it will save on the local machine store as following

and if everything works fine, the CM console will look like:

and the resource explorer:

System Center Configuration Manager 2012 - TechNet Virtual lab

Raphael — Fri, 27 Jan 2012 10:59:00 GMT

Hi All,

for those that want to play with CM12 and doesn't have time (or resources) do build its own lab...there a few to play online...

http://go.microsoft.com/?linkid=9796179 - TechNet Virtual Lab: System Center 2012 Configuration Manager: Application Management

http://go.microsoft.com/?linkid=9796558 - TechNet Virtual Lab: System Center 2012 Configuration Manager: Content Management

http://go.microsoft.com/?linkid=9796564 - TechNet Virtual Lab: System Center 2012 Configuration Manager: Managing Clients

http://go.microsoft.com/?linkid=9796561 - TechNet Virtual Lab: System Center 2012 Configuration Manager: OSD Bare Metal

http://go.microsoft.com/?linkid=9796019 - TechNet Virtual Lab: System Center 2012 Configuration Manager: Advanced Software Distribution

http://go.microsoft.com/?linkid=9796016 - TechNet Virtual Lab: System Center 2012 Configuration Manager: Basic Software Distribution

http://go.microsoft.com/?linkid=9795894 - TechNet Virtual Lab: System Center 2012 Configuration Manager: Software Updates

http://go.microsoft.com/?linkid=9796038 - TechNet Virtual Lab: System Center 2012 Configuration Manager: Endpoint Protection RC

http://go.microsoft.com/?linkid=9793970 - TechNet Virtual Lab: Migrating from Configuration Manager 2007 to Configuration Manager 2012

http://go.microsoft.com/?linkid=9793971 - TechNet Virtual Lab: Introduction to System Center Configuration Manager 2012