Fix wrong parameter displayed in the drop down box when running converted reports in Configuration Manager
SQL Reporting Services is by far the best choice for working with reports in Configuration Manager 2007. As a built-in feature you can convert all your existing classical ASP reports. This will for most reports work like a charm. But for some reports, you will have to do a little work after the conversion.
1. One minor change I often perform is fixing the parameter shown in drop down boxes. As you can see from this report “Status of a specific advertisement”, I’m getting a list of advertisement ID’s and not the advertisement name.
2. To fix the problem, open the Reporting Services website. Find the report, click the drop down box and select Edit the report with SQL Reporting builder 3.0 (requires SQL Server 2008 R2).
3. An installation of SQL Reporting Builder 3.0 will automatically launch.
4. The report will open in design mode
5. Click Parameters and open the properties for AdvertID parameter.
6. Click Available Values and in the label field, select AdvertisementName.
7. Click OK and close the properties.
8. Run the report and the list of names should be shown instead of the ID values.
9. Finally click Save and the report changes will be saved.
/Kent
Newsletter Update – Modifying the Lite Touch Wizard – Part II
If you like what you see, keep on reading…
A while back I did a post on how to modify the Lite Touch wizard and here is the next part. Once more it is customer that wanted some hardware information before installing the OS on the machine, most of the properties is already in the system but some does not exist. The way to solve that is to create a userexit script, which is VB script that runs as part of customsettings.ini. It exists, runs the script and returns the value and assigns it to a custom property
So, here is an sample of a userexit “thing” in customsettings.ini
[Settings]
Priority=Init, Default
Properties=MyCustomProperty, CPUName
[Init]
CPUName=#SetCPUName()#
UserExit=HardwareInfo.vbs
So, here is what happens. ZTIgather will read the “Settings” section, it finds the “Priority” and then it finds the “Init” section. So it jumps to the “Init” section and then it runs the “hardwareinfo.vbs” script, it looks for a function called “SetCPUName”. It runs that and return the value into the property called CPUName
So, if we then create a Wizard pane we can now display that value, or we could use CPUname like any other Property.
Read the complete story here
http://deploymentbunny.com/2011/05/26/modifying-the-lite-touch-wizard-in-mdt-2010-sample-2/
http://deploymentbunny.com/2011/04/27/modifying-the-litetouch-wizard-in-mdt-2010-sample-1/
/mike
Configure MDT 2010 to send an email when deployment is completed
A while ago I and fellow MVP Mikael Nystrom created a small vbscript that sends an email when the deployment is completed….here it is J
Download ZTISendmail
Instructions
1. Download and extract the ZTISendmail.zip file to a folder, say D:\ZTISendMail
2. Using Deployment Workbench, create an application using the following settings
a. Application with source files
b. Application Name: ZTISendMail
c. Source Directory: D:\ZTISendMail
d. Specify the name of the directory that should be created: ZTISendmail
e. Command Line: cscript.exe ZTISendMail.wsf
f. Working Directory: .\Applications\ZTISendmail
3. Add the ZTISendmail application as the final step of the task sequence (see below screenshot)
4. Configure your rules (customsettings.ini) using sample customsettings.ini file (content below).
