FEP Install on a multisite SCCM2007 infrastructure
read this to understand FEP-Client installation on a multisite Hirarchy of SCCM 2007
In: FEP, sccm · Tagged with: FEP, sccm
Collect the Monitor Serial Numbers for your CMDB Part2
Create a Report for looking the Clients Monitors
insert this:
SELECT DISTINCT
v_r_system.netbios_name0 AS “Computer Name”,
v_gs_system_enclosure.serialnumber0 AS “Serial Number”,
v_GS_PC_BIOS.serialnumber0 AS “PC Bios Serial Number”,
v_gs_computer_system.manufacturer0 AS “Computer Manufacturer”,
v_gs_custominventoryinfo.model0 AS “Monitor Model”,
v_gs_custominventoryinfo.SerialNumber0 AS “Monitor SN”
FROM v_gs_processor
INNER JOIN v_r_system
ON v_gs_processor.resourceid = v_r_system.resourceid
INNER JOIN v_gs_system_enclosure
ON v_gs_system_enclosure.resourceid = v_r_system.resourceid
INNER JOIN v_GS_PC_BIOS
ON v_GS_PC_BIOS.resourceid = v_r_system.resourceid
INNER JOIN v_gs_computer_system
ON v_gs_computer_system.resourceid = v_r_system.resourceid
INNER JOIN v_gs_custominventoryinfo
ON (v_gs_custominventoryinfo.resourceid = v_r_system.resourceid)
have fun, All information is provided “as is” without any warranty! Try in lab before. Handle with
In: Reporting, sccm, scripts · Tagged with: monitor, serial, WMI
Collect the Monitor Serial Numbers for your CMDB Part1
First you have to install the WMI- Provider, written by Roger Zander
Download Versions x86/x64: http://sourceforge.net/projects/wmimonitor/files/wmimonitor/V1.0.0.3/
Implement to SCCM and Push the installatio on every Client.
Test it with the WMI-Command (read in Rogers Blog)
Modify the sms_def.mof file on all Primary Sites.
You can find the File in ‘%Program Files%\Microsoft Configuration Manager\inboxes\clifiles.src\hinv’
(copy first that you have a Backup)
Add the following on the File, search for “Software Metering’s List of recently used apps”
and past it after this section.
//————————————————
// Moitor informations
//————————————————
#pragma namespace (“\\\\.\\root\\cimv2\\sms“)
class win32_MonitorDetails
{
[key]
string Monitor_Details;
};
#pragma namespace (“\\\\.\\root\\CIMv2\\sms“)
[ SMS_Report(TRUE),
SMS_Group_Name("MonitorDetails"),
SMS_Class_ID("Microsoft|CustomInventoryInfo|1.0"),
Namespace("\\\\\\\\.\\\\root\\\\CIMv2")
]
class win32_MonitorDetails : SMS_Class_Template
{
[SMS_Report(TRUE),key]
string Model ;
[SMS_Report(TRUE),key]
string SerialNumber ;
};
to controll view the log “%Program Files%\Microsoft Configuration Manager\logs\dataldr.log” on the Primary site that you edit the sms_def.mof
it should be everything fine, or you have a entrance that sccm backups the old sms_def.mof.bak file
Go to the Client with the SCCM-Client-Center tool and start the HW-Inventory (Full), contol on the client in the log “c:\windows\system32\ccm\logs\inventoryagent.log” to see if Win32_monitordetails details are inside.
Start the Recource Explorer and have a look on “MonitorDetails”
have fun, All information is provided “as is” without any warranty! Try in lab before. Handle with care in production
In: client, Discovery, sccm, scripts · Tagged with: monitor, serial, sms_def.mof, WMI
Windows 8 Devloper preview online
Have Fun on youre first look on Windows 8 
http://msdn.microsoft.com/en-us/windows/apps/br229516
In: Win8 · Tagged with: Win8, Windows 8
FEP 2010 Rollup
FEP 2010 Rollup more Win OS Versions:
http://www.microsoft.com/download/en/details.aspx?id=26583
FEP 2010 Rollup Tools (FEP GPOs in AD GPOs):
http://www.microsoft.com/download/en/details.aspx?id=26613
Antivirus exclusions by MS best Practice
http://social.technet.microsoft.com/wiki/contents/articles/953.aspx
have fun
Windows Thin PC Released
Have a look on this new Windows Thin PC
http://www.microsoft.com/windows/enterprise/solutions/virtualization/products/thinpc.aspx
you can download the Trial here: Download the 90-day trial.
asap I will test and post for Deploy it over SCCM on Clients that you would like connect a VDI Farm on med-V, Citrix and VM-Ware
have fun
unattended.xml and the secret of Language
There are some articles on my blog about the Language settings in unattended File. in this Post I will talking about the hole understanding, I hope you can follow me 
if you open the ImageX-tool that is installed on your WAIK infrastructure you can easily create an unattend.xml file with click and dirty.
But there are more inside for understanding. The Language (MUI) in Win7 are completely new designed, for first you have to understand this http://technet.microsoft.com/en-us/library/dd744336(WS.10).aspx
than we can have a look to a situation in my self: In Switzerland we have tree Languages in the different parts of country, German, France, Italy there are also different Keyboard Layouts for this tree, and some installations of Software are in English. Its not easy to deploy all this in one setup, but with Win7 is it possible.
On TechNet are an article with the settings for the hole Unattended.xml understanding, we want to have a look only in the Language settings
If you have set all your language settings in the File the same as like this:
<UserLocale>de-CH</UserLocale>
For the Settings by Users first login, if you would like first Use with an Swiss-France User set it to fr-CH
Read more: UserLocale Specifies the per-user settings used for formatting dates, times, currency and numbers.
<SystemLocale>de-CH</SystemLocale>
The basic Unicode Language
Read more: SystemLocale Specifies the language for non-Unicode programs.
<InputLocale>de-CH; fr-CH; it-CH</InputLocale>
That’s the tree languages in Switzerland, but you have also install the Language packs of all this Languages, you can do this by different Ways: dism, Tasksequence like this http://blog.colemberg.ch/2011/03/how-i-can-implement-w7-os-languages-zero-touch-via-sccm-os-capturing/
Read more: InputLocale Specifies the system input locale and the keyboard layout.
<UILanguage>en-US</UILanguage>
That’s the Language for default if you have to install Software in the TS that needs “Program Files” and not “Programme” you can set the default
Read more: UILanguage Specifies the system default user interface (UI) language.
<UILanguageFallback>de-DE</UILanguageFallback>
If your Language settings has more than one fallback language set it to your default Language, there are possible to point it to all your Language Pack integrated Languages.
Read more: UILanguageFallback Specifies the fallback language if the system default UI language is only partially localized.
And you run the first Deployment with the new Unattend.xml in Tasksequence, in the middle you will become a screen to select your Language, after this the Tasksequence runs finish.
There a very important sentence in all of the links on the top:
“If this value is configured in the oobeSystem configuration pass, the Regional Settings page of Windows® Welcome will be skipped.”
So you have to change the Language settings in an other section from the specialize to oobeSystem!
Have fun: All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.
In: OSD, sccm, Tasksequence, Win 7 Design · Tagged with: OS-Deployment, Task Sequence, unattended
can not install ccmsetup (80004005, 1603)
Your installation of SCCM Agent is failed with the following command in a multisite hierarchy:
"\\<SCCM-Server>\SMS_<Site-code>\Client\ccmsetup.exe" SMSSLP=<Central-Site FQDN> DNSSUFFIX=<DNSsuffuix> SMSMP=<Primary-Site FQDN>
MSI: Action 13:16:12: CcmInitializePolicy. Initializing policy ccmsetup 30.06.2011 13:16:12 1456 (0x05B0)
MSI: Action 13:16:12: SmsSetClientConfigInit. Setting SMS configuration ccmsetup 30.06.2011 13:16:12 1456 (0x05B0)
MSI: Setup failed due to unexpected circumstances
The error code is 80004005 ccmsetup 30.06.2011 13:16:12 1456 (0x05B0)
Installation failed with error code 1603 ccmsetup 30.06.2011 13:16:12 1456 (0x05B0)
Next retry in 120 minute(s)… ccmsetup 30.06.2011 13:16:12 1456 (0x05B0)
for better read:
MSI: Action 13:16:12: SmsSetClientConfigInit. Setting SMS configuration ccmsetup
MSI: Setup failed due to unexpected circumstances
The error code is 80004005 ccmsetup
Installation failed with error code 1603 ccmsetup
Next retry in 120 minute(s)…
There is a problem in the translation of the log-file, the red marked means that Management Point are wrong (SMSMP)
So delete the Management Point command or correct the command and run again…
All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.
In: client, Errors, sccm · Tagged with: client, install, sccm
Install FEP 2010 fails with “Windows Firewall Configuration Provider” error
Have you any Problem to install FEP2010 agent, there is a service that you must uninstall before you can install FEP, also in a Virus-scanner migration scenario!
have you ever installed Wondows Intune on a client-computer you have remove it?
In this list are all the things that intunes installas on your client-machine http://onlinehelp.microsoft.com/en-us/windowsintune/ff628133.aspx
you have to remove all this Programs and agents
- Windows Intune Center
- Microsoft Easy Assist
- Microsoft Online Management Policy Agent
- Windows Firewall Configuration Provider
- Microsoft Policy Platform
- Windows Intune Endpoint Protection Agent
- Windows Intune Endpoint Protection
- Windows Intune Monitoring Agent
- System Center Operations Manager 2007 R2 Agent
- Microsoft Online Management Update Manager
- Microsoft Online Management Client
The important to remove fist is the yellow marked application.
After that the installation of FEP is no more a problem.
in a case that you migrate from Symantec Endpoint Protection 11 to FEP 2010 there are other things that you have to uninstall.
The Symantec Live Update Agent should be removed from the client: "C:\Program Files\Symantec\LiveUpdate\LSETUP.exe" -a -s -q – u
In caste that you have a Password save for uninstall SEP11 Client, you can change the Regkey: “HKLM\Software\Symantec endpoint protection\Protection\AV\AdministratorOnly\Security” /v UseVPUninstallPassword /d 0 /t REG_DWORD /f
All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.
