Blog – Dries Willems – Freelance IT Consultant

http://ccmexec.com/2015/03/changing-startup-to-automatic-on-the-sccm-remote-control-service/

Windows 10 comes with .NET framework 4.5 pre-installed, but many apps developed in Vista and Windows 7 era require the .NET framework v3.5 installed along with 4.5.

These apps will not run unless you will install the required version.

When you try to run any such app, Windows 10 will prompt you to download and install .NET framework 3.5 from the Internet.

Here is how to install it offline using DISM from Windows Kits for Windows 10.

Dism /Get-WIMInfo /WimFile:S:\Temp\install.wim

Dism /Mount-WIM /WimFile:S:\Temp\install.wim /Index:1 /MountDir:S:\Temp\offline

Dism /Image:S:\Temp\offline /Enable-Feature /FeatureName:NetFX3 /All /Source:H:\sources\sxs /LimitAccess

Dism /Image:S:\Temp\offline /Add-Package /PackagePath:S:\Temp\de-de

Dism /Image:S:\Temp\offline /Add-Package /PackagePath:S:\Temp\fr-fr

Dism /Image:S:\Temp\offline /Add-Package /PackagePath:S:\Temp\nl-nl

Dism /Unmount-WIM /MountDir:S:\Temp\offline /Commit

Dism /Cleanup-WIM

Remove the following file”C:\Windows\System32\GroupPolicy\Machine\Registry.pol”

run gpupdate /force

When you open registry editor and connect to a remote system, the only hives you will see are HKEY_LOCAL_MACHINE and HKEY_USERS. The other two hives, HKEY_CLASSES_ROOT and HKEY_CURRENT_USER are there too, but are under the two visible hives. So for all purposes, I am only going to explain here how to access the once that are not openly evident.

HKEY_CLASSES_ROOT

This hive is located under HKEY_LOCAL_MACHINE\SOFTWARE\Classes

HKEY_CURRENT_USER

This hive is more tricky to find because you have to correlate what the SID is to the user. This can be done by going to HKEY_USERS and parsing through each SID. Ignore the SIDs that have only 4 sets of numbers (i.e. S-1-5-18). These are system accounts. The best way I found to parse through and find who the user is is to go to HKEY_USERS\<SID>\Software\Microsoft\Windows\CurrentVersion\Run. Under this key will be a list off applications that are set to run when the system is booted up. You can look at the data field and there will usually be a few apps that will say “c:\users\<username>”, which will give away who the user of that SID is.

There is another way and that would be to remotely run a WMI query to find out who the current user is and the SID for that user.

http://mickitblog.blogspot.be/2012/03/accessing-all-hives-from-remote.html

Dism /mount-wim /wimfile:s:\winpe\boot_W10_x64.wim /index:1 /mountdir:s:\winpe\mount

Dism /image:s:\winpe\mount /add-driver /driver:s:\winpe\drivers /recurse

Dism /image:s:\winpe\mount /Set-InputLocale:nl-BE

Dism /image:s:\winpe\mount /Set-SysLocale:nl-BE

Dism /image:s:\winpe\mount /Set-UserLocale:nl-BE

Dism /Unmount-Wim /MountDir:s:\winpe\mount /Commit

Dism /Cleanup-WIM

Get-ADUser -SearchBase ‘OU=DEV,OU=BuitenDienst,OU=Users,OU=Moto,DC=Com’ -Filter * | ForEach-Object {Add-ADGroupMember -Identity ‘GG_SDS_DEV_Caris_ML_PROD’ -Members $_ }

http://oxfordsbsguy.com/2015/03/09/powershell-how-to-add-all-users-in-an-ou-to-a-security-group-using-get-aduser-and-add-adgroupmember/

ConsoleSetup.exe /q TargetDir=”%ProgramFiles(x86)%\Microsoft Configuration Manager\AdminConsole\” EnableSQM=0 DefaultSiteServerName=SCCMP.CORP.ME

%ProgramFiles(x86)%\Microsoft Configuration Manager\AdminConsole\bin
Microsoft.ConfigurationManagement.exe
5.0.8239.1000

@echo off

msiexec /I vc_red.msi TRANSFORMS=vc_red.mst /qn ALLUSERS=1 /L*v %windir%\temp\TEST_SDS_Microsoft_VC++RedistSU_2008SP1_1.0_EN_x86_Inst.log REBOOT=REALLYSUPPRESS

if %errorlevel% == 3010 (exit /b 0) else (exit /b %errorlevel%)

Take ownership on the last Folder

Give your account full control

Delete the folder

This does only work after you apply

dism /get-MountedWimInfo

dism /cleanup-wim

Query test
sp_configure ‘clr enabled’

Query change
sp_configure ‘show advanced options’, 1;
GO
RECONFIGURE;
GO
sp_configure ‘clr enabled’, 1;
GO
RECONFIGURE;
GO

https://msdn.microsoft.com/en-us/library/ms131048.aspx

When you migrate the Orchestrator database from one instance of Microsoft SQL Server to another and then try to open Orchestrator Designer in Microsoft System Center 2012 Orchestrator or in System Center 2012 R2 Orchestrator, Orchestrator Designer starts to open and then generates a prompt that indicates that the license key has expired. When you enter a valid key and then click OK, the same prompt appears.

For all the details as well as a resolution, please see the following:

KB2920037 – Orchestrator Designer generates a prompt for a license key after you migrate the Orchestrator database (http://support.microsoft.com/kb/2920037)

To resolve this issue, follow these steps:

Stop the Orchestrator Management service.

Open the Orchestrator database on the new instance of SQL Server.

Open a new query, and make sure that the Orchestrator database is selected.

Execute the following two lines on the database, one at a time:

Delete the old key:

[Microsoft.SystemCenter.Orchestrator.Cryptography].[DropOrchestratorKeys]

Create the new key:

[Microsoft.SystemCenter.Orchestrator.Cryptography].[CreateOrchestratorKeys]

Start the Orchestrator Management service.

When you now open Orchestrator Designer, you are again prompted for the key. When you enter the key, the key works as designed.

http://blogs.technet.com/b/orchestrator/archive/2014/01/09/kb-orchestrator-designer-generates-a-prompt-for-a-license-key-after-you-migrate-the-orchestrator-database.aspx

When attempting to set up and configure the ConfigMgr 2012 site system role for reporting services, a frequently experienced “problem” is that the instance name can be blank/empty in the wizard and thereby unable to proceed with the wizard. This usually occurs when SRS has not been pre-configured properly.
While it is common “knowledge” that the reporting services database needs to be created first, an oft-overlooked step is to use the Reporting Services Configuration Manager to create the virtual directories for IIS. And it is these steps which need to be completed to get you on your way.
Open Reporting Services Configuration ManagerConnect to the server/instanceClick on Web Service URL – make a fake change, such as changing the name of the virtual directory and then putting it back to ReportServer – and clicking Apply. This will then create the new virtual directories.
Click on Report Manager URL – again, make a change to the name and put back to just Reports – and click Apply to generate the new virtual directories.Close configuration managerReturn to the CM12 site role setup program, click “Verify” for the database connection, and voila the instance is now populated correctly!

http://myitforum.com/myitforumwp/2012/10/10/reporting-services-site-role-setup-instance-blankempty/#

Problem:

I am trying to remove a DP from a server. I’ve gone to Administration | Overview | Site Configuration | Servers and Site System Roles

I right-click on the server that is hosting the DP I want to remove and select Delete from the context menu.

However, I then get a Delete Server dialog box stating:

The server “\\<server_fqdn>” cannot be deleted because it contains the following site system roles:

Component server

The component server role supports other site system roles and is created automatically by Configuration Manager. Although there might be a delay, this role is automatically removed after you remove other site system roles on this server.

I’ve tried right-clicking on the Component server role under Site System Roles but the Remove Role option is greyed out so I’m unable to remove the Component Server Site System Role.

As this server is only hosting a DP I don’t understand why it has the Component server installed on it.

Resolution:

The server in question must have had another Site System role installed on it at some point in the past as the Component server role gets installed on a server whenever a Site System role is installed with the exception of a DP (so if the server has only ever run as a DP you will not see the Component server).

Chances are a role other than the DP was installed at some point in the past and removed but the Component server role hasn’t been removed for some reason.

The quickest way to kickstart this is on the affected server:

Right-click Site system under Site system Roles and select Properties from the context menu.

Make a change to a setting on the Site system properties screen such as checking the Require the site server to initiate connections to this site system then click OK.

Wait 10 – 15 minutes.

Refresh the console and the Component server role should now have disappeared.

You should now be able to delete the server hosting the DP.

– See more at: http://www.faqshop.com/wp/configmgr/cm12/cm12trobshoot/cm12sitesys/unable-remove-component-server-site-system-role#sthash.VzDrv9CV.dpuf

http://www.faqshop.com/wp/configmgr-2012-unable-remove-component-server-site-system-role

http://blogs.technet.com/b/configmonkey/archive/2013/11/13/deploying-configmgr-hotfixes.aspx#_Operating_System_Deployments

<?xml version=”1.0″ encoding=”utf-8″ ?>
<!– Oobe.xml sample file for the region: Catalonia, Spain
For more info, see Configure Oobe.xml,
http://go.microsoft.com/fwlink/?LinkId=317086 –>
<FirstExperience>
<oobe>
<oem>
<name>Fabrikam</name>
<!– Name of the manufacturer –>

<eulafilename>fabrikam_eula.rtf</eulafilename>
<!– If a relative path is used, it will start from the same folder as Oobe.xml.
Example: %WINDIR%\System32\Oobe\Info\Default\1031\fabrikam_eula.rtf –>
</oem>

<defaults>
<!– Set the defaults for the language, location, locale, keyboard, and timezone –>
<language>1027</language>
<!– App language.
See Available Language Packs for Windows, Language decimal identifier
http://go.microsoft.com/fwlink/?LinkId=206620 –>

<location>217</location>
<!– Country or region where the PC is deployed.
See Table of Geographical Locations, Geographic location identifier (decimal)
http://go.microsoft.com/fwlink/?LinkId=141804 –>

<locale>1034</locale>
<!– PC locale. Determines sorting, time/date formatting, and keyboards/IMEs.
See Default Input Locales for Windows Language Packs, keyboard decimal identifier:
http://go.microsoft.com/fwlink/?LinkId=325349 –>

<keyboard>0000080a</keyboard>
<!–Keyboard layout.
Use the keyboard value list in the registry under
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Keyboard Layouts,
or see Windows Language Pack Default Values, keyboard pair:
http://go.microsoft.com/fwlink/p/?LinkId=262262 –>

<timezone>Central Europe Daylight Time</timezone>
<!– Use the time zone list in the registry under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones –>

<adjustForDST>true</adjustForDST>
<!– Use this to adjust the time for Daylight Savings Time –>

</defaults>
</oobe>
</FirstExperience>

OSD Task Sequence

Run Performance Indicator
WinSAT.exe formal
%SystemRoot%\System32

select * from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.Name like “ALM%”

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like “%XXX%” and SMS_G_System_ADD_REMOVE_PROGRAMS.Version < “11.0.10” order by SMS_R_System.Name

copy /y NUL C:\Windows\Temp\SDT_Microsoft_Windows_10_EN_Deployed.txt >NUL

Rename the language pack folder within the install directory of your Management console.

System Center Configuration Manager 2012:
C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\{language_code}

Close the management console.

Rename the language pack folder corresponding to your situation.

In my case it is nl.

Rename it to nl_backup.

Restart your console.

When creating a desktopshortcut for Office 2013 keep the following in mind.

Use [ under Start in:

Target:

[Excel 2013]

Location:

[DesktopFolder]

Name:

Excel 2013

Start in:

[

Arguments

Shortcut
Key:

None

Run:

Normal windows

Office:

Set KMS Host

cscript OSPP.VBS /sethst:KMS.FQDN.local

C:\Program Files (x86)\Microsoft Office\Office15

—-

Activate Product

cscript OSPP.VBS /act

C:\Program Files (x86)\Microsoft Office\Office15

—-

Install for non windows-kms server

office2013volumelicensepack_x86_en-us.exe

http://www.microsoft.com/en-us/download/details.aspx?id=35584

————

Windows:

Set KMS Host

cscript slmgr.vbs /skms KMS.FQDN.local:1688

C:\Windows\System32

—-

Activate Product

cscript slmgr.vbs /ato

C:\Windows\System32

—-

PowerShell.exe -command “& { $ReturnCode = (New-Object -COMobject wscript.shell).popup(\”NO OSDprocessorArchitecture defined. Device ‘ll be formated, but no OS ‘ll be installed!\”,0,\”Warning\”,0x00040016); eXit $ReturnCode}”

Test Step – Check if OS Architecture is defined!

http://msdn.microsoft.com/en-us/library/ms645505(VS.85).aspx​

Tasksequence variable bij options

_____

PowerShell.exe -ExecutionPolicy ByPass -Command “& { (New-Object -COMobject wscript.shell).popup(\”Entered a OSDTestStep, OSDTestRun is activated. Press OK to Continue. \”,0,\”Information\”,0x00040041); eXit $ReturnCode}”​

Run command line

Wpeutil SetKeyboardLayout 0813:00000813

or with powershell

Set-WinUserLanguageList nl-BE

or with DISM
See other post

0x87D00324

This will indicate that software installation was succesfull, but detection method sucks.

$sharepath = “C:\SWL”

$Acl = Get-ACL $SharePath

$AccessRule= New-Object System.Security.AccessControl.FileSystemAccessRule(“Users”,”full”,”ContainerInherit,Objectinherit”,”none”,”Allow”)

$Acl.AddAccessRule($AccessRule)

Set-Acl $SharePath $Acl

Over the last couple of months I gathered the following tweaks for a better performance insight the virtual machine, besides disabling / uninstalling useless services and devices:

– Disable the pre-logon screensaver:

Open Regedit

HKEY_USERS\.DEFAULT\Control Panel\Desktop

Change the value of “ScreenSaveActive” to 0.

– Disable updates of the last access time attribute for your NTFS filesystem, especially for i/o intensive vm’s this is a real boost:

Open CMD

fsutil behavior set disablelastaccess 1

– Disable all visual effects:

Properties on your desktop

Appearance -> Effects

Disable all options.

– Disable mouse pointer shadow:

Control Panel -> Mouse

Click on the tab “pointers” and switch “enable pointer shadow” off.

– Uninstall Tablet PC Components, unless this feature is needed.

– Disable IPv6, unless it is needed.

– Use the File System Utility (fsutil) command to disable the setting that keeps track of the last time a file was accessed.

For example: fsutil behavior set disablelastaccess 1

– Start the Registry Editor (regedit.exe) and change the TimeOutValue REG_DWORD in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Disk to0x000000be(190).

– Shut down the guest operating system and power off the virtual machine.

Change the virtual machine video card RAM setting to 128 MB.

Power on the virtual machine.

https://pubs.vmware.com/view-50/topic/com.vmware.view.administration.doc/GUID-E712DAE6-88DF-4208-BEFA-09513A01A26E.html

Virtual Machine tweaks for a better performance

OSDDisableFeatures.ps1

DISM /online /Disable-Feature /FeatureName:MediaCenter /Quiet /NoRestart

write-host “Successfully removed Media Center”

DISM /online /Disable-Feature /FeatureName:FaxServicesClientPackage /Quiet /NoRestart

write-host “Successfully removed Windows Fax and Scan”

DISM /online /Disable-Feature /FeatureName:OpticalMediaDisc /Quiet /NoRestart

write-host “Successfully removed Windows DVD Maker”

http://tweaks.com/windows/40255/manage-windows-features-from-command-line-with-dism/

With this method you don’t have to import a computer in SCCM 2012 with the MAC-Address.

Just start the tasksequence as an unknown computer …

To do this, complete the following steps, if you need any assistance, just post a comment at the bottom of this post.

Open your Configuration Manager console and go to the Assets and Compliance Workspace and then click on Device Collections.

Right click on the collection you want to deploy the OS to then click Properties (for this guide I’m using All Unknown Computers). You then need to click on the Collection Variables tab.

Click on the new button as circled below:

In the variable name type OSDCOMPUTERNAME and leave the value areas blank and then click ok.

Once you have this collection variable in your collection property settings, you can then deploy your OSD task sequence to this collection and you will be prompted to enter your computer name.

– See more at: http://www.techygeekshome.co.uk/2012/12/prompt-for-computer-name-during-sccm-osd.html#sthash.5fguzzbD.dpuf

http://www.techygeekshome.co.uk/2012/12/prompt-for-computer-name-during-sccm-osd.html

This task sequence variable can be used to configure a post action for a task sequence. To configure this, follow the next steps:

• Open a task sequence in the Task Sequence Editor.
• Add a Set Task Sequence Variable –step to the task sequence.
• Fill in as Task Sequence Variable SMSTSPostAction and, in this example, as Valuecmd /c shutdown /s /t 0 /f.
• Close the Task Sequence Editor.

http://www.petervanderwoude.nl/post/how-to-perform-an-action-directly-after-the-task-sequence-is-finished-with-configmgr-2012/

HKLM\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Certificates\6BFF5439A57586FEF61B8D8E2194A96DD459B511

Apply Operating System English
Apply Operating System French
Apply Operating System Dutch
Use an unattended or Sysprep answer file
-> PKG_Win8.1_Unattend_NL
—> Unattend.xml

Apply Language EN (OSLanguage equals “EN”)
Apply Language FR (OSLanguage equals “FR”)
Apply Language NL (OSLanguage equals “NL”)
-> Apply NL Language Pack
—> cmd /c dism.exe /online /add-package /packagepath:lp.cab
—> Package: PKG_Microsoft_LanguagePack_Win8.1_01.00_NL -> lp.cab
-> BCDEdit to NL
—> cmd /c bcdedit /set {current} locale nl-NL
-> BCDBoot to NL
—> cmd /c bcdboot %WinDir% /l nl-NL
-> Remove EN-US
—> cmd /c reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MUI\UILanguages\en-US /f
-> Restart Computer

You can identify if the computer is Laptop or Desktop based on its chassis Types.

Below are listed the Chassis types available to create SCCM collection or reports.

For Laptops Chassis Types : 8 , 9, 10, 11, 12, 14, 18, 21

For Desktop Chassis Type : 3, 4, 5, 6, 7, 15, 16

For server Chassis Type: 23

Below is the collection to list all the computers which are laptops which fall in above Chassis type. All these values are from SQL table called SMS_G_System_SYSTEM_ENCLOSURE .If you are looking to create SCCM report,you can create using Views(v_GS_SYSTEM_ENCLOSURE).

You can also replace the values with Desktop computers or servers also you can use joins to club these with AD groups for deploying the applications based on this.

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes in ( “8”, “9”, “10”, “11”, “12”, “14”, “18”, “21” )

Here are some sample reports/queries available which you can make use of it

http://myitforum.com/cs2/blogs/snorman/archive/2007/09/18/count-of-chassis-types-by-collection.aspx

http://wmug.co.uk/wmug/b/eskonr/archive/2010/11/16/sccm_2d00_collection_2d00_to_2d00_list_2d00_all_2d00_the_2d00_laptop_2d00_computers

HKEY_CLASSES_ROOT\Installer\Products

of

HKLM\Software\Classes\Installer\Products

COL_Devices_without_ClientUpdate_2012R2CU3

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = “x64-based PC” and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.DisplayName = “CCM Framework” and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version >= “5.00.7958.1000” and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version < “5.00.7958.1401”

COL_Devices_with_SCCM_Console

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like “%System Center 2012 R2 Configuration Manager Console%”

For 64-bit OS also use
or SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName like “%Applicationname%”

Redistribute a hidden package.

Apply the following powershell script

$SiteCode = “XXX”
$PackageID = “XXX00003”
$distpoints = Get-WmiObject -Namespace “root\SMS\Site_$($SiteCode)” -Query “Select * From SMS_DistributionPoint WHERE PackageID=’$PackageID'”
foreach ($dp in $distpoints)
{
$dp.RefreshNow = $true
$dp.Put()
}

https://social.technet.microsoft.com/Forums/en-US/d2e5366f-f7c3-4691-9011-ad35ed25ab74/configuration-manager-client-upgrade-package-missing?forum=configmanagerdeployment&prof=required

Rules in MDT Media

–> bootstrap.ini
[Settings]
Priority=Default

[Default]
SkipBDDWelcome=YES
KeyboardLocale=080c:0000080c
KeyboardLocalePE=080c:0000080c

–> Customsettings.ini

[Settings]

Priority=Default

Properties=MyCustomProperty

[Default]

OSInstall=Y

SkipCapture=YES

SkipAdminPassword=NO

SkipProductKey=NO

BitsPerPel=32

VRefresh=60

XResolution=1366

YResolution=768

SkipBDDWelcome=YES

SkipApplications=YES

SkipAppsOnUpgrade=YES

SkipBitLocker=YES

SkipUserData=YES

UserDataLocation=NONE

SkipTaskSequence=NO

SkipComputerBackup=YES

SkipComputerName=NO

SkipDomainMembership=YES

JoinWorkgroup=WORKGROUP

SkipSummary=YES

SkipFinalSummary=YES

SkipLocaleSelection=YES

KeyboardLocale=080c:0000080c

KeyboardLocalePE=080c:0000080c

UserLocale=fr-be

UILanguage=fr-be

SkipTimeZone=Yes

TimeZoneName=Romance Standard Time

FinishAction=SHUTDOWN

PXE keeps rebooting after “preparing Network connection”. Errors: “reply has no message header marker”, “Failed to get client identity (80004005)”, “Failed to request for client”

OSD Boot media cannot see TS

Resolution: Set correct time in BIOS!

cmd:
date
time

http://777notes.wordpress.com/2012/10/09/sccm-2012-failed-to-get-client-identity-80004005/

You can keep your operating system images updated with the latest software updates from Microsoft using the offline servicing feature of Configuration Manager. Here are a few facts you may not know:

Software updates content is not retrieved over the wide area network, rather it is obtained locally from the Configuration Manager content library on the site server where offline servicing is performed. This prevents excessive network traffic during the application of updates.

You can specify to continue if an error occurs while applying the selected updates to an OS image. As a result, if some updates fail to be applied to the image, servicing will apply the remaining updates.

Upon completion of the offline servicing process, you can specify that the updated version of the OS image is automatically distributed to all distribution points where it resides.

Offline servicing stages temporary data on the site server when the process runs, and uses the drive on which Configuration Manager is installed. One common request is to configure offline servicing to use the specified drive of the site server. Let’s say you want to specify the “F:” drive for offline servicing to stage and mount the OS image and store software updates files. Here’s how to do this using the Windows Management Instrumentation Tester utility (wbemtest.exe).

Launch wbemtest.exe.

Connect to the Configuration Manager namespace on the site server. For example, if your site code is “CCP”, connect to namespace “root\sms\site_CCP”.

Next click Query, enter the following, and then click Apply:

SELECT * FROM SMS_SCI_Component WHERE SiteCode=’CCP’ AND ItemName LIKE ‘SMS_OFFLINE_SERVICING_MANAGER%’

Double-click on the result.

Double-click on the “Props” property in the list.

Click “View Embedded”.

There will be four entries returned in the list. Double-click on each to find the one where the PropertyName field is “StagingDrive”.

Change Value1 in the list to “F:” (in this example).

Click “Save Object”.

Click “Close”.

Click “Save Property”.

Click “Save Object”.

Click “Close”.

Now the next time offline servicing runs it will stage all of its files in the folder F:\ConfigMgr_OfflineImageServicing.

–Vladimir Sorokin

http://blogs.technet.com/b/configmgrteam/archive/2013/07/15/customizing-offline-servicing-of-operating-system-images.aspx

1: Scan for updates
powershell.exe -command “([wmiclass]’root\ccm:SMS_Client’).TriggerSchedule(‘{00000000-0000-0000-0000-000000000113}’)”

2: Wait for Scan to Finish
powershell.exe -command start-sleep 500

3: Install All Updates

4: Restart Computer

Re-apply these steps 3 times

Today’s blog post is a collaboration between our PFE group and premier support. Joao Botto (PFE), Kyle Blagg (PFE), and Scott McArthur (Support) are writing about their favorite device. You will see this post in the askpfeplat and askcore blogs.

Some of you may know that we launched Surface Pro 3 before its gigabit network adapter and Docking Station were available, and that has led to some customers experiencing issues such as:

· Slow PXE performance downloading a boot.wim

· Surface Pro 3 not charging when in docking station

Both of these issues are due to older firmware. When you unbox a Surface Pro 3, there will be newer firmware available, due to the time difference between when the device is manufactured and finally makes its way to you.

This post focuses on the Surface Pro 3, but this same process can be utilized on the Surface Pro and Surface Pro 2 (but not the Surface RT/Surface 2 devices).

If you are deploying a custom image using Microsoft Deployment Toolkit (MDT), System Center Configuration Manager, or other deployment tool you may want to address these firmware issues before you deploy your custom image. We have developed a method to use a USB Windows PE drive that automatically updates the Surface firmware when you boot with it.

Other possible workarounds, instead of using the method describe in this blog post are to have a boot.wim on a USB drive instead of PXE, or go through OOBE and immediately use Windows Update to apply the latest Surface drivers/firmware.

Introduction

Firmware updates reprogram the chips inside your device, making it better than ever before. They are shipped in what we call capsules, but they look like regular drivers:

image

If this interests you, check out the blog post from the Surface Team about how Windows Update Makes Surface Better

Before you start this recipe you will need the following ingredients:

Latest Surface Pro Firmware Updates from the driver pack

Windows Assessment and Deployment Kit (ADK), specifically the Deployment Tools and Windows PE components of this kit

A USB flash drive

IMPORTANT:

· Do not try to update the Touch Firmware using this method.

· This guidance will not work if the Surface Pro disk was formatted (and a new Operating System wasn’t loaded) or if the disk is encrypted.

· To prevent accidental device shutdown, the firmware updates will only be applied when the device has 40% or more of battery. We strongly recommend you fully charge your battery before proceeding with the firmware update.

Drivers

Extract the Surface driver pack you previously downloaded, and select the EC, SAM and UEFI firmware updates. All these firmware capsules are in the Microsoft > FW folder.

image

Copy the EC, SAM and UEFI the firmware files to a folder. In my example I called this folder Pro3 and put it in C:\SurfaceFW\Pro3

Reminder: DO NOT try to update touch firmware using this process.

image

Windows PE

From the ADK you must make sure you have installed the Deployment Tools and Windows PE:

image

From that point you will have the Deployment and Imaging Tools Environment (which is essentially a command line window with additional tools in the path). Run it as Administrator.

image

At this point you’re ready to start preparing a version of Windows PE x64 that will be used to update the firmware. It’s very important to use the x64 version since x64 UEFI isn’t able to load an x86 OS.

When you install the ADK the default folder (on a x64 install of Windows) for Windows PE is C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Pre-installation Environment

In that folder you will find the WinPE images for x86 and x64, and some scripts that make the creation of a WinPE flash drive extremely easy.

image

Change directory to this folder: cd “C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment”

From the elevated prompt you will have to start by running the first script by executing the command copype amd64 C:\WinPE_amd64 to place the original WinPE image in that folder.

Then you will use the same elevated prompt to run MakeWinPEMedia /UFD C:\WinPE_amd64 E: (the E: drive is my flash drive, which will be reformatted, and C:\WinPE_amd64 is the working folder I supplied in the previous command).

image

The first step is to create a folder (in my case c:\mount), and then mount the mount the WinPE image using this command: dism /Mount-Image /ImageFile:E:\sources\boot.wim /index:1 /MountDir:c:\mount

image

Then you should inject the firmware updates into Windows PE: dism /Image:C:\mount /Add-Driver /Driver:C:\SurfaceFW\Pro3 /Recurse

You should see all firmware updates being successfully injected.

image

Note: Make sure all three firmware updates were successfully injected into Windows PE. You should see the “The driver package was successfully installed” message like in the example above.

To unmount the WinPE image just run the following command:

dism /Unmount-Image /MountDir:C:\mount /commit

image

You can now boot to your new WinPE environment by plugging the flash drive to your new Surface Pro (while it’s turned off) and then start the device with Power + Volume Down. Keep holding the volume down button until a few seconds after your device displays the Surface logo. Once WinPE loads, you’ll see a blank screen and a command prompt will automatically process the updates.

The firmware will be updated without any user interaction and your Surface will reboot automatically when it’s done. You will then see “Please wait while we install a system update” for a few minutes and your Surface Pro 3 will reboot again when it’s ready.

If you want to validate that the update was successful you can boot into the UEFI settings (start the device by pressing Power + Volume Up) and look under device information. If you see the Asset Tag field that would indicate your UEFI firmware was updated from the version that shipped in the original image. Over time this method may not be usable for validation since at some point the image that is shipped with the device will already have this version of the firmware by default. Another option for validating firmware versions is to press Shift+F10 at the first page of the OOBE and open devmgmt.msc to check the firmware versions. Note: If you use this process to update the firmware and then goto Windows Update, you will likely see a firmware update offered. This is normal. The firmware is updated but the driver currently installed is not up to date. The offered update will install the driver that shows the updated firmware

We will be improving this process over time so look for updates to this blog for some additional features such as automatically checking for battery level and other ways to determine the firmware was updated.

Scott “I fix all Surface Issues” McArthur, Kyle “my Surfaces are on TV” Blagg, and Joao “let’s do it!” Botto

http://blogs.technet.com/b/askpfeplat/archive/2014/10/20/how-to-update-the-surface-pro-3-firmware-offline-using-a-usb-drive.aspx

By simply adding a unique text file to the driver folder it creates a different hash value and allows you to import the same driver even if the actual drivers already have been imported.

Just put the above code into a batch file at the root of your directory structure for a given model and name it for that hardware model; e.g., name it Optiplex755.bat and put it in the root of the folders housing the Optiplex 755 drivers.

—————————————–

@ECHO OFF

for /f “tokens=*” %%G IN (‘dir /ad /b /s’) DO (

echo. > “%%G\%~n0.txt”

)

—————————————–

Executing this simple batch file will create an empty text file named Optiplex755.txt in every sub-directory.

Repeat as necessary for each model and each model’s top-level driver folder.

If you add or change any drivers for a model, just re-execute the script.

http://myitforum.com/cs2/blogs/jsandys/archive/2010/04/05/duplicate-drivers-helper-script.aspx
https://wbracken.wordpress.com/2009/09/26/adding-duplicate-drivers-to-sccm-sp1/

This registry editing trick has been around forever, but still works in ConfigMgr 2012! In fact, it’s the preferred way to keep the ConfigMgr client software from installing on specific computers in your organization.

A couple NOTEs: This only blocks ConfigMgr client software when using the site-wide automatic push method. You can still use any other method to install the client, ex. manually running CCMSetup.exe. Also, this does not exclude the computer from being “discovered”, just that the client software will not be installed once it is discovered liked non-excluded computers.

To do it…

On the ConfigMgr site server, run the Registry Editor.

Navigate to the SMS_DISCOVERY_DATA_MANAGER sub-key which is located within HKEY_LOCAL_MACHINE/Software/Microsoft/SMS/Components/SMS_DISCOVERY_DATA_MANAGER

Locate the ExcludeServers key and edit the Multi-String value.

Enter the NetBIOS name of each computer you want to exclude. Each computer name must be on its own separate line.

Hit OK and close out the Registry Editor.

http://myitforum.com/myitforumwp/2012/02/01/same-as-before-excluding-specific-computers-from-becoming-configmgr-2012-clients/

File
xcopy fzdefaults.xml “%ProgramFiles(x86)%\FileZilla FTP Client\fzdefaults.xml”* /I /S /Y /C /R

xcopy *.ora “c:\oracle\product\11.2.0\client_86\network\admin\”* /I /S /Y /C /R

Folders & Subfolders
xcopy .\swl\*.* C:\SWL /I /S /Y /C /R

Main Installer

http://myITforum.com/myitforumwp/wp-content/uploads/2012/06/SCCMRCT1.0.zip

Updates for 2012

http://myITforum.com/myitforumwp/wp-content/uploads/2012/06/2012Update1.0.EXE.zip

Fixes the issue with restarting the ConfigMgr Agent Host on the client tools

http://myITforum.com/myitforumwp/wp-content/uploads/2012/06/2012Update1.21.exe

Fixes the issue with performing an Application Deployment Evaluation Cycle on both clients and collections

http://myITforum.com/myitforumwp/wp-content/uploads/2012/09/2012Update1.34.exe

Fixes the issue with files being copied to the wrong location.

https://social.technet.microsoft.com/Forums/en-US/c5aaaa8e-cdd8-400b-8749-8a233a3f0a52/importing-existing-computers-into-a-device-collection?forum=configmanagergeneral&prof=required

ConfigMgr 2012 – Powershell Right Click Tools Version 2.0

https://psrightclicktools.codeplex.com/

It’s possible to change the size of the blocks used for the Trivial File Transfer Protocol (TFTP) transfer; the larger the block size, the greater the performance. Microsoft’s recommendation is to not set higher than 16384; in addition, you must use multiples of 4096, such as 8192, 16384, and so on. I got a huge performance boost from using a value of 16384. Perform the following steps:

Log on to the Configuration Manager PXE Windows Deployment Services (WDS) server.

Open the registry editor (regedit.exe).

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP.

From the Edit menu, select New, DWORD value.

Enter a name of RamDiskTFTPBlockSize and press Enter.

Double-click the new value.

Set the Base to Decimal and set the value (e.g., 16384).

Click OK.

Restart the WDS server service.

http://windowsitpro.com/configuration-manager/speed-sccm-tftp-performance-pxe-clients

Task Sequence problem after SCCM 2007 to SCCM 2012 R2 migration

Ran into some problem after I had migrated a SCCM 2007 site to SCCM 2012 R2 CU3

When running the Task Sequence I got the following errors in SMSTS.LOG

Empty location for package: _SMSTSXXX000F1 ApplyOperatingSystem

Installation of image 1 in package XXX000F1 failed to complete..

The system cannot find the file specified. (Error: 80070002; Source: Windows) ApplyOperatingSystem

Changing the operating system package properties under Data Access to “Copy the content in this package to a package share on distribution Points” would have been the solution to this problem.

My client had a problem with an update of Adobe Reader version 11.
After updating, only english was available.
The update was a MUI version …

After verifying the files and folders, I noticed that the “Locale” folder wasn’t created.
I installed Adobe Reader 11 MUI normaly (not in silent mode) and choose another language then English.
After the installation just copy the “Locale” folder in the Program folder of Adobe Reader.
C:\Program Files (x86)\Adobe\Reader 11.0\Reader\Locale

I copied the “Locale” folder into the Customization Wizard and overwrote all files.

Computer Configuration (Enabled)

Policies

Administrative Templates

Policy definitions (ADMX files) retrieved from the central store.Windows Components/Internet Explorer/Security Features/Add-on Management

Policy Setting Comment

Add-on List Enabled

Add-on List

{761497BB-D6F0-462C-B6EB-D4DAF1D92D43} 0

{DBC80044-A445-435B-BC74-9C25C1C588A9} 0

w32tm /configure /manualpeerlist:”be.pool.ntp.org” /syncfromflags:manual /reliable:yes /update

net stop w32time

net start w32time

w32tm /resync /rediscover

Just like former BMW’s the 1 series has a hidden OBC menu. This can be accessed with the car started or “on”. Make sure you read the bottom instructions on how to unlcok all the menus. Below are the instructions and menus:

For ‘navigation’ in the menu’s, use the ‘mileage reset button’.

To get IN the menu’s push that button for approx. 15 sec.

Keep it pressed until you get the “01.__” in the display between the RPM and speedo-meter.

“XX.YY” means the menu-numbers.

If you want increase the “XX” part, push the ‘mileage reset’ button for approx. 2 sec.

As soon as you see “XX.__”, you can increase XX by pressing the ‘mileage reset’ button.

Every ‘push’ increases “XX”. If you want to increase the “YY”, when the display shows,

for example “01.00”, then every ‘push’ on the ‘mileage reset’, will increase the “YY” value.

01.00 FGSTNR = “Fahrgestellnummer” (Chassisnumber)

01.01 K-ZAHL W/T

01.02 BMWTNR

01.03 COD DIA

01.04 KI HSTL DATUM = “Herstellungs Datum” (Manufactured/Assembled on date…)

01.05 ???

01.06 SW

01.07 KODIERDATEN

01.08 CAN

02.00 KI TEST = Dashboard test. All light, gauges, displays and so on will light up,

move…. works only when the engine is NOT running.

03.00 ??? (maybe it will show something after your first ‘service’, motor oil change)

04.00 MOM VBR = actual fuel consumption

04.01 RW-VBR-MOM = fuel consumption per hour

05.yy average fuel consumption

06.00 how much you have in your ‘tank’ in liters. Left- and Right compartment and Total

06.01 dito in hex?

07.00 KTMP-MOM = Temp. Cooling Fluid (Celsius)

07.01 ATMP-MOM = “Aussentemperatur” Temp. Outside (Celsius)

07.02 dito in hex?

07.03 N-MOT-MOM = RPM

07.04 N-VWF-MOM = max. RPM at the moment

08.00 V-EFF = exact speed

08.01 V-ANZ = “Anzeige” speed shown on dash

08.02 V-SZ

08.03 D-GESCHW 1 WEG

08.04 D-GESCHW 1 ZEIT

08.05 D-GESCHW 2 WEG

08.06 D-GESCHW 1 ZEIT

09.00 Voltage

10.00 KM/WOCHE

11.00 ??? , has to do how the time will be displayed

11.01 km or miles

11.02 Celcius or Fahrenheit

11.03 how to display fuel consumption. km/l or l/100km or mpg

12.00 V-ANKUNFT = arrival time 12.01 ANK-ZEIT = time of arrival

13.00 AUDIO = all(?) sounds. Like the ‘boing’ of the ‘light on warning’

14.00 FS EINTRAEGE = error messages (if any)

15.00 Ports?

16.00 Dashboard lighting.

17.00 Temp inside in the car??

18.00 CC-TEST = you can see some of the ‘check control’ messages.

Look also at the iDrive screen!

19.00 UNLOCK

20.YY to 23.YY ???

That UNLOCK stuff is also important.

If not UNLOCKed, you can only see menu’s 01 and 02.

In the ’19’ menu you must ‘click-in’ a unlock code.

That code you can calculate from the “FGSTNR” number.

You must add the last 5 figures of that FGSTNR number. for example:

: XXXXXX12345 the unlock code will be: 1+2+3+4+5=15

20.YY to 23.YY There is more to discover……

Backup Registry
REG EXPORT HKLM\Software\Microsoft\COM3 %temp%\com.reg /y

Change Registry Key
REG ADD HKLM\Software\Microsoft\COM3 /v REGDBVersion /t REG_BINARY /d 010000 /f

Move Computer to New OU
wscript.exe Move_Comp_To_OU.vbs “OU=New,OU=Computers,OU=XX,DC=XX,DC=XX”
Disable 64-bit file system redirection
PKG_XX_OSD_Scripts
XX.XX\srv-dom

Restore Registry Backup
REG IMPORT %temp%\com.reg

root\cimv2
SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE “%DELL%”

root\cimv2
SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “%CF-53%”

root\cimv2
SELECT * FROM Win32_BaseBoard WHERE Product LIKE “%P5B-TMX%”

root\cimv2
SELECT * FROM Win32_ComputerSystem WHERE Systemtype LIKE “%x64%”

Quick check

run
-> wmic baseboard get product,manufacturer
-> wmic computersystem get model,name,manufacturer,systemtype
-> wmic diskdrive get model

Copy Fonts to Temp
xcopy *.ttf %SystemDrive%\Temp /Y /I /Q
PKG_XX_XX

Set PowerShell Execution Policy
Powershell.exe -noprofile -command “Set-ExecutionPolicy Bypass LocalMachine” -force

Run Add-Font.ps1
Powershell.exe -noprofile -file Add-Font.ps1 -path “%SystemDrive%\Temp”
PKG_XX_OSD_Scripts

Revert PowerShell Execution Policy
Powershell.exe -noprofile -command “Set-ExecutionPolicy RemoteSigned LocalMachine” -force

Remove C:\Temp
cmd.exe /c rmdir “%SystemDrive%\Temp” /S /Q

AD:

The AD Computer object must fill in the ManagedBy field with the Primary User

The AD User must be added to a AD User Group

SCCM:

System Discovery has to be extended with the ManagedBy field

User Discovery has to be extended with the Distinguishedname field

SCCM Collection Query:

select
SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client
from SMS_R_System where SMS_R_System.managedBy in (select
SMS_R_User.distinguishedName from SMS_R_User where SMS_R_User.UserGroupName =
“DOMAIN\\GG_SDC_Manufact_App_11.0_01.01_EN_INSTALL”) order by
SMS_R_System.Name

Windows 7:

Install Package KB958830

cmd /c start /w pkgmgr /iu:RemoteServerAdministrationTools-Roles-AD-DS-SnapIns;RemoteServerAdministrationTools-Roles-AD-DS;RemoteServerAdministrationTools-Roles-AD;RemoteServerAdministrationTools-Roles;RemoteServerAdministrationTools

run batfile ==>

@echo off

hostname.exe > __t.tmp

set /p host=<__t.tmp

del __t.tmp

c:\windows\system32\netdom.exe remove /d:mydomain %host% /ud:mydomain\serviceaccount /pd:P@ssw0rd

Windows Server 2012 R2:

DISM /online /enable-feature /featurename=ActiveDirectory-Powershell /all

@echo off

hostname.exe > __t.tmp

set /p host=<__t.tmp

del __t.tmp

c:\windows\system32\netdom.exe remove /d:data %host%

PS H:\> $appv=get-appvclientpackage -name *visio*
PS H:\> $appv

PackageId : 7828a894-5155-4f3d-923e-a0b91ce5835c
VersionId : a6ec2f50-114b-4cee-ba42-277cb70b6f46
Name : SDV_Microsoft_VisioPrem_2010SP2_01.00_EN
Version : 0.0.0.1
Path : C:\WINDOWS\ccmcache\57\SDV_Microsoft_VisioPrem_2010SP2_01.00_EN.appv
IsPublishedToUser : True
UserPending : False
IsPublishedGlobally : False
GlobalPending : False
InUse : True
InUseByCurrentUser : True
PackageSize : 1671256007
PercentLoaded : 100
IsLoading : False
HasAssetIntelligence : True

PS H:\> Start-AppvVirtualProcess -FilePath cmd.exe -AppvClientObject $appv

http://support.microsoft.com/kb/2830069

1. Install OffVirt

Office2010AppVKit-x64.exe
http://www.microsoft.com/en-us/download/details.aspx?id=10386

msiexec /i OffVirt.msi ADDLOCAL=OSpp,OSpp_Core,OSppWoW64 PROPLUS=1 VISIOPREM=1 PIDKEYS=CK796-QYJ67-JVKWX-QJ9GD-W3CKX USEROPERATIONS=1

2. Download and Extract the Office 2010 sequencing kit for App-V

Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0.EXE
http://www.microsoft.com/en-us/download/details.aspx?id=38399

3. Start the App-V Sequencer

Click on Tools -> Options…

Open the “Exclusion Items” tab and add the following:

[{Common AppData}]\Microsoft\OfficeSoftwareProtectionPlatform

[{Common AppData}]\Microsoft\Windows

With Mapping Type = “VFS”

Run Powershell(x86) as an Administrator

Enter-PSSession -ComputerName LAP123 -Credential Labo\Admin

Get-AppvClientPackage -All

Unpublish-AppvClientPackage

PackageId

VersionId

Remove-AppVClientPackage

PackageId

VersionId

Don’t forget to remove the folder in the SCCMcache!
\\LAP123\c$\Windows\ccmcache\..

get-hotfix | Where-Object {$_.HotFixID -match “KB2835517”}

wusa.exe “Windows6.3-KB2835517-x64.msu” /quiet /norestart /log:%WINDIR%\Temp\Install_SDC_Microsoft_MediaPack_1.0_01.00_ML.log

wusa.exe /uninstall “Windows6.3-KB2835517-x64.msu” /kb:KB2703761 /quiet /norestart /log:%WINDIR%\Temp\Uninstall_SDC_Microsoft_MediaPack_1.0_01.00_ML.log

_____________________________________________________________

<span class=”rem”>’Returns info if Windows Management Framework 3 in installed</span>

<span class=”rem”>’ ———————————————————-‘ </span>

<span class=”kwrd”>Option</span> Explicit

<span class=”kwrd”>Dim</span> objWMIService, strComputer

strComputer = <span class=”str”>&quot;.&quot;</span>

<span class=”rem”>’Run the query</span>

<span class=”kwrd”>Set</span> objWMIService = GetObject(<span class=”str”>&quot;winmgmts:&quot;</span> _

&amp; <span class=”str”>&quot;{impersonationLevel=impersonate}!\\&quot;</span> _

&amp; strComputer &amp; <span class=”str”>&quot;\root\cimv2&quot;</span>)

<span class=”kwrd”>Dim</span> QFEs

<span class=”kwrd”>Dim</span> QFE

<span class=”kwrd”>Set</span> QFEs = objWMIService.ExecQuery (<span class=”str”>&quot;Select * from win32_QuickFixEngineering where HotFixID like ‘KB2506143’&quot;</span>)

<span class=”kwrd”>For</span> <span class=”kwrd”>Each</span> QFE <span class=”kwrd”>in</span> QFEs

Wscript.echo <span class=”str”>&quot;Update KB2506143 was installed by &quot;</span> &amp; QFE.InstalledBy &amp; <span class=”str”>&quot; on &quot;</span> &amp; QFE.InstalledOn

<span class=”kwrd”>Next</span>

WScript.Quit

DE: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language\InstallLanguage” (REG_SZ) equals “0407”

EN: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language\InstallLanguage” (REG_SZ) equals “0409”

FR: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language\InstallLanguage” (REG_SZ) equals “040C”

NL: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language\InstallLanguage” (REG_SZ) equals “0413”

setup.exe /Q /W /I setup.ini

msiexec /X {5783F2D7-D028-0409-0100-0060B0CE6BBA} MSIRESTARTMANAGERCONTROL=Disable /qb-!

http://forums.autodesk.com/t5/DWG-TrueView/DWG-Trueview-2013-silent-installation-on-different-path-Windows/td-p/3467892

http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=9078813

——————-

http://www.itninja.com/software/xmind/xmind/3-5187

http://www.xmind.net/download/win/

Installation:

xMind 3.1.1.exe /S

Deinstallation:

%ProgramFiles%\XMind\uninstall.exe /S

No Upadate:

you have to create and copy the org.xmind.cathy.prefs file.

The file must include following rows:

eclipse.preferences.version=1

checkUpdatesOnStartup=false

and copy it to:

%AppData%\XMind\workspace-cathy\.metadata\.plugins\org.eclipse.core.runtime\.settings

No Dialog on Startup:

like no update. You need following rows in the net.xmind.verify.prefs file:

SUPPRESS_SIGN_IN_DIALOG_ON_STARTUP=true

eclipse.preferences.version=1

and copy it also to:

%AppData%\XMind\workspace-cathy\.metadata\.plugins\org.eclipse.core.runtime\.settings\

for version 3.2.1

in the “net.xmind.verify.prefs”

STARTUP_SIGN_IN_DIALOG_SHOWED=false

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes]
“DefaultScope”=”{012E1000-F331-11DB-8314-0800200C9A66}”
“KnownProvidersUpgradeTime”=hex:1c,21,6c,bd,bf,2b,cf,01
“Version”=dword:00000003
“UpgradeTime”=hex:e4,ab,d7,bd,bf,2b,cf,01

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes\{012E1000-F331-11DB-8314-0800200C9A66}]
“DisplayName”=”Google”
“URL”=”http://www.google.com/search?q={searchTerms}&sourceid=ie7&rls=com.microsoft:{language}:{referrer:source}&ie={inputEncoding?}&oe={outputEncoding?}”
“ShowSearchSuggestions”=dword:00000001
“SuggestionsURL”=”http://clients5.google.com/complete/search?q={searchTerms}&client=ie8&mw={ie:maxWidth}&sh={ie:sectionHeight}&rh={ie:rowHeight}&inputencoding={inputEncoding}&outputencoding={outputEncoding}”
“FaviconURL”=”http://www.google.com/favicon.ico“
“FaviconPath”=”C:\\Users\\vantorre\\AppData\\LocalLow\\Microsoft\\Internet Explorer\\Services\\search_{012E1000-F331-11DB-8314-0800200C9A66}.ico”

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
“Deleted”=dword:00000001

Troubleshooting tips for client communication to the Application Catalog:

Ensure that the Configuration Manager client is successfully assigned to a site and operational by checking LocationServices.log and ClientIDManagerStartup.log.

Verify that the client can communicate with the management point. For example, check out any HTTP errors in the CcmMessaging.log file.

Check the LocationServices.log file for any errors during the time you browsed to the Application Catalog. One typical reason for Application Catalog failures in this log is client communication failures to the management point, indicated by the following error: “Failed to send web service info Location Request Message.” In this case, verify that the management point is operational and reachable from the client computer.

If you have recently installed the Application Catalog roles, the configuration on the site system server might take some time to complete. If you have a central administration site, make sure that sites are replicating successfully. In this scenario, information about the Application Catalog roles must replicate to the central administration site and then back to the primary site before the Application Catalog is fully operational. For example, until the replication is complete, users will not be able to request or install applications from the Application Catalog.

Ensure that the domain and user name that is displayed in the top right corner of the Application Catalog matches the user that is logged in to Windows, especially if Internet Explorer prompts the user for credentials.

Ensure that any required Internet Explorer plugins are enabled and not explicitly blocked in Internet Explorer. For more information, see Prerequisites for Client Deployment in Configuration Manager on TechNet.

If you have configured client settings to add the URL to the trusted sites and the URL is not added to the trusted sites zone, check whether the client successfully downloads client policy and also check group policy settings in your environment to ensure that the Configuration Manager client can add the URL to the trusted sites zone.

If the Application Catalog shows an error page, the error will also be displayed in the ConfigMgrSoftwareCatalog.log. You can find the log file by searching the user profile folder. For example, in Windows 7, you can find the log file inside the following folder:

%systemdrive%\Users\<username>\AppData\LocalLow\Microsoft\Silverlight

Note that the error in this log most likely indicates one of the issues mentioned previously.

If you see the following error message when you request or install software in the Application Catalog, ensure that the domain and user name that is displayed in the top right corner of the Application Catalog matches the user that is logged in to Windows. If you are prompted for a user name and password, do not specify a different account from the one that you used to log in to Windows. In addition, you will see the same error message if the client setting Install permissions prevents you from installing software (for example,this setting is configured for Only administrators and your account is not a member of the local Administrators group).

Last week it was needed to install printer drivers on already deployed Windows 7 systems. Because driver packages can be used only during OS deployment (within a task sequence) that was not an option. Lucky me I found another way for doing this, just use the PnPutil command to do this. Let’s have a look at the needed steps now!

Create a new software package (instead of a driver package) without a program, and per model. Add all the packages created to a task sequence, using the “Run command line” option. Put in a name, select the needed package (created before), select a account with enough permissions (because drivers cannot be installed with the system account afterwards), and add a command line:

xcopy *.* C:\Temp\Drivers\ /I /S /Y /C /R

from Package

cmd.exe /c PnPutil.exe -i -a C:\Temp\Drivers\*.inf

After that all .inf files available in the package will be scanned and needed drivers installed cq. injected in the Windows 7 driver store. In my opinion a very easy solution to install (printer) drivers on already installed systems. Hope it helps!

Source: danovich.com.au > Thanks for sharing!

http://henkhoogendoorn.blogspot.be/2013/07/deploy-printer-drivers-during-configmgr.html

select * from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion = “Microsoft Windows NT Workstation 6.3” and SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = “Adobe Reader XI (11.0.05) MUI”

Object type	Collection resources	Deployment	Application Catalog	Software Center
Application	Users or groups	Available deployment, does not require approval	Yes	After installation is initiated successfully from the Application Catalog
Users or groups	Available deployment, requires approval	Yes	After the application is approved
Users or groups	Required deployment	No	Yes
Computers	Available or required deployment	No	Yes
Package and program	Users or groups	Available deployment	Yes	After installation is initiated successfully from the Application Catalog
Users or groups	Required deployment	No	Yes
Computers	Available or required deployment	No	Yes

http://blogs.technet.com/b/configmgrteam/archive/2012/03/31/introducing-the-application-catalog-and-software-center-in-system-center-2012-configuration-manager.aspx

Reminder for myself 😉

Device Collection:
select * from SMS_R_System where SMS_R_System.SystemGroupName = “DATA\\GG_SDC_IBM_Notes_ML_PROD”

User Collection (managedby):
select SMS_R_USER.ResourceID,SMS_R_USER.ResourceType,SMS_R_USER.Name,SMS_R_USER.UniqueUserName,SMS_R_USER.WindowsNTDomain from SMS_R_User where SMS_R_User.DistinguishedName in (select SMS_R_System.managedBy from SMS_R_System where SMS_R_System.SystemGroupName = “DATA\\Domain Computers”) and SMS_R_User.UserGroupName = “DATA\\GG_SDV_FreeMind_FreeMind_ML_PILOT”

AD Computer Object: Managedby field must be filled in!

Reminder for myself 🙂

During OS Deployment

Before your hard drive is formatted and partitioned

X:\windows\temp\smstslog\

After your hard drive is partitioned formatted

X:\smstslog\ and then is in C:\_SMSTaskSequence\logs\smstslog\

Within Windows

Within Windows before the SCCM agent is installed:

C:\_SMSTaskSequence\logs\smstslog\

Within Windows after the SCCM agent installed:

C:\windows\system32\ccm\logs\smstslog\

When the Task Sequence completes on a x86

C:\windows\system32\ccm\logs\

For x64 Systems

C:\windows\SysWOW64\ccm\logs\

You will need to enable your boot.wim with f8 support to retrieve the log if it bombs out before apply OS stage so that you can bring up the command prompt and copy the log to a share on the network.

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Google\Chrome] “SyncDisabled”=dword:00000001

You need to enable the StartUp Pages in the GPO. Enable Action on startup and the other, URLs to open at startup and enter the URL(s) you want to open.

and use GPO for settings

master_preferences does not work on 32.0 …

Use the same OS when using DISM!

Offline Image:
Dism /Get-WIMInfo /WimFile:C:\Temp\install.wim
Dism /Mount-WIM /WimFile:C:\Temp\install.wim /Name:”Windows 8.1 Enterprise N” /MountDir:C:\Temp\offline
Dism /Image:C:\Temp\offline /Enable-Feature /FeatureName:NetFX3 /All /Source:D:\sources\sxs /LimitAccess
Copy languages to C:\Temp
Dism /Image:C:\Temp\offline /Add-Package /PackagePath:C:\Temp\de-de
Dism /Image:C:\Temp\offline /Add-Package /PackagePath:C:\Temp\fr-fr
Dism /Image:C:\Temp\offline /Add-Package /PackagePath:C:\Temp\nl-nl
Dism /Unmount-WIM /MountDir:C:\Temp\offline /Commit

Current Image:
Dism /Online /Enable-Feature /FeatureName:NetFX3 /All /Source:D:\sources\sxs /LimitAccess

Remember:
First add NetFX3 and add the languages later

dism windows 8.1 netfx3 80070490
Error when running DISM /Online /Cleanup-Image /RestoreHealth – error 0x800f0906
How to troubleshoot error 0x800F081F when installing roles and features
http://blogs.technet.com/b/askcore/archive/2012/05/14/windows-8-and-net-framework-3-5.aspx
http://support.microsoft.com/kb/2785188

I just did a screen replacement on an Iphone 4S and have checked all connections they are all good, blue resistor is still there. Everything else works fine, WIFI signal is great etc.

Problem is that it doesn’t recognize if I remove or insert the SIM card and all I get at the top of the screen is Searching…

I searched 4 hours on this particular problem.

Soo here it is –>

When you replace a lcd screen on an iPhone 4S with iOS 6.X, make sure you change the time to current! (Auto -> manual)

The default time when replacing the battery is 01 : 01 1 jan 1970.

This problem is related to iOS 6!

greetings 😉

I can’t boot from a Windows 7 USB pen drive on my iMac begin 2008 (shortname IM81)

Verify Apple Computer Version on wikipedia http://en.wikipedia.org/wiki/Intel_iMac

If you have only 2 options in the boot camp assistant, or if bootcamp doesn’t recognize the windows installer disk when its on a bootable usb, it’s because bootcamp doesn’t recognize your MAC as a model that should install windows from a USB, its actually quite easy to fix, just follow these simple steps:

1. go to Applications>Utilities> right click on boot camp and click Show Package Conents, you’ll find a folder inside called Contents. Inside that folder exists a file called info.plist.

2. Right click on the folder containing the file > get info > change permissions so any user can read & write. Do the same for the file itself (right click > get info…).

3. Right click on info.plist and choose Open with > Text Edit.

4. at the end of the document theres a list of strings that contain different versions of Mac computers, the list is titled something like: “USB boot Versions”, add your Mac’s version to the string list ( MB40 ) if your version is Macbook 4,1 (you can see this by clicking on the System information App in the Utilities folder).

5. save the file and change back the permissions on the file and folder.

Now open boot camp and you should see the option to create a Windows 7 installler on a USB, and also bootcamp will look for a windows installation on any USB’s after you partition the hard drive.

That should get you past the bootcamp assistant phase, assuming your usb is indeed bootable, your mac should partition the disk and boot into the USB and start the installation (for some reason mine doesn’t recognize the USB as bootable but thats another issue)

FYI: Windows Official ISO’s http://www.mydigitallife.info/official-windows-7-sp1-iso-from-digital-river/

The kerberos SSPI package generated an output token of size 12750 bytes, which was too large to fit in the token buffer of size 12000 bytes, provided by process id 4.

The output SSPI token being too large is probably the result of the user willdrie901@INTRA.*.*.* being a member of a large number of groups.

It is recommended to minimize the number of groups a user belongs to. If the problem can not be corrected by reduction of the group memberships of this user, please contact your system administrator to increase the maximum token size, which in term is configured machine-wide via the following registry value: HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters\MaxTokenSize.

How to fix this …

REGEDIT:

HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters

create New DWORD: “MaxTokenSize” with decimal value “48000”

reboot your machine

download (and launch with administrative privileges) http://blog.gentilkiwi.com/mimikatz (trunk version for last version)

privilege::debug (or not if you’re already system)

crypto::patchcng (nt 6)

crypto::exportCertificates CERT_SYSTEM_STORE_LOCAL_MACHINE “CA”

crypto::exportCertificates CERT_SYSTEM_STORE_LOCAL_MACHINE “My”

crypto::exportCertificates CERT_SYSTEM_STORE_LOCAL_MACHINE “…”

pfx files are passwords protected “mimikatz”

Greetings 😉

System.Net.WebException: The request failed with HTTP status 407: Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied. ).~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)

Solution

Remove following keys from the registry HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings

HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\InternetSettings\Connections\SavedLegacySettings

Driver for “DP BACKPLANE SCSI Enclosure Device”

DellBPA05.exe (110KB)

http://www.dell.com/support/drivers/us/en/555/DriverDetails/DriverFileFormats?c=us&l=en&s=&cs=555&DriverId=R220657

Drivers Broadcom BCM5709S NetExtreme II GigE iSCSI Adapter Windows 2003

http://www.broadcom.com/support/license.php?file=NXII/win_2k3_2k8-14.4.8.4.zip

Microsoft Storport Hotfix KB957910

A Windows Server 2003 SP2-based iSCSI boot server cannot generate dump files if the server uses a Storport virtual miniport as the LUN controller

http://support.microsoft.com/kb/957910

Broadcom BCM5709S NetXtreme II GigE iSCSI Adapter

B06BDRV\L4SC&PCI_163A14E4B06BDRV\L2ND&PCI_163A14E4PCI\VEN_14E4&DEV_163A
Code 37

We had a problem installing Windows Server 2003 on a vm with LSI Logic Parallel but came up with a BSOD with message 0x…07B

So the Harddrive wasn’t recognized.

Here is the driver for vmware esxi 4.1

http://www.lsi.com/downloads/Public/SCSI%20HBAs/SCSI%20HBAs%20Common%20Files/LSI20320-R_xp_50700_01034132IT_1201800_1005239.zip

enjoy 😉

Installatie OS op USB stick

In de volgende stappen bespreken we hoe je Microsoft Hyper-V Server 2008 R2 installeert op een USB stick.

Voorbereiding

Om dit proces te vervolledigen moet je de volgende zaken hebben.

– Een USB stick met minstens 8GB aan schijfruimte (Dit is de minimum vereiste voor Hyper-V Server 2008 R2

– ISO Hyper-V Server 2008 R2

– Windows Automated Installation Kit (WAIK)

– Een PC die Windows 7 of Windows Server 2008 R2 heeft

– De server moet een x64 processor hebben

1. Start CMD op als administratorWe maken een VHD op driveletter F: met een grootte van 14500 MB.

Een vast ingestelde grootte staat voor een betere performantie)

Diskpart

create vdisk file=F:\virtualharddisk.vhd maximum=14500 type=fixed

select vdisk file=F :\virtualharddisk.vhd

attach vdisk

list disk

select disk disknumber

create partition primary

select partition 1

active format fs=ntfs quick

assign

laat dit venster open en start een nieuwe CMD op als administrator 

2. Download en installeer Windows AIK from Microsoft (1.7 GB).

Hieruit haal je ImageX dat je straks nodig hebt.

3. Uit de WIM file haal je de versies die je nodig hebt

imagex /info E:\sources\install.wim

4. nu ga je terug naar de diskpart cmd

diskpart

select vdisk file=F:\virtualharddisk.vhd

attach vdisk

list volume

5. We kopieren de bootfiles van de vhd naar de USB stick.

bcdboot D:\Windows /s F: /v

6. Wanneer dit gedaan is keer je terug naar de cmd met diskpart

detach vdisk

exit

When installing a core server like Hyper-V Server or a regular windows server 2008 core you may have the problem that not all drivers are installed.

I installed hyper-v server on a dell system and thee network drivers weren’t installed.

The options are …

– slipstream the drivers in the iso

– install drivers from an usb stick via cmd

– …

just type in cmd

rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 c:\”where your inf file is located”

check your driveletters if you use a cd or usb stick

If that didn’t work … no worries

I placed the driver files on my c dir

(adding files to a core server ???? … I took the HDD and placed it in an Sata quickport pro from Sharkoon)

run cmd as administrator

these were my broadcom drivers

pnputil -i -a c:\b57nd60a.inf

pnputil -i -a c:\k57nd60a.inf

🙂

Aanpassingen in VagCom

1. meebranden achterlichten bij dagrijverlichting

zowel pré-facelift als facelift A6

Dit heet ook wel “landencode 2”. In de auto zijn diverse programmeringen van de lampen aanwezig, afhankelijk van wettelijke voorschriften in de markten waar de A6 wordt geleverd. Onder “landencode 2” is het meebranden van de achterlichten bij dagrijverlichting opgenomen, voor de Scandinavische markt.

stuurgroep 09

functie 07

laatste cijfer op “2” zetten

kies “test”

kies “save”

kies “done, go back”

OK

2. bevestigingstoon van alarm bij vergrendelen

zowel pré-facelift als facelift A6

In het Duits de DWA Quitterungston. Dit werkt alleen bij af-fabriek aanwezig alarm.

stuurgroep 46

functie 07

bij de laatste vier cijfers 2048 optellen

kies “test”

kies “save”

kies “done, go back”

0131825

0133873

OK

3. vrijschakelen “hidden menu”

zowel pré-facelift als facelift A6, programmering pré-fl is anders!

Dit werkt alleen bij MMI+. In het hidden menu kun je veel instellingen wijzigen. Wees je er wel van bewust, dat dit een soort broncode of rootmenu van de auto is, en dat je dus ook heel veel fout kunt doen…

control module 5F

adaptation 10

channel 6

verander “0” in “1”

kies “test”

kies “save”

kies “done, go back”

Openen van hidden menu na vrijschakelen:

zet MMI in willekeurig welk menu, met uitzondering van ‘CAR’

druk ‘setup’ in en houdt vast

druk ‘car’ er bij in en houdt samen zo’n 5 seconden vast

MMI-scherm verandert naar nieuw menu

OK

4. opheffen snelheidsbeveiliging DVD-scherm (“video in motion”, VIM)

alleen facelift A6

Af fabriek gaat het MMI-scherm in de DVD-kijk-stand bij beweging van de auto op zwart. Deze beveiliging heet “video in motion”. De snelheidswaarde waarbij het scherm uitgaat, blijkt via VAG-COM / VCDS aan te passen te zijn!

Hiervoor heb je een code nodig die je via Internet kunt achterhalen.

control module 5F

advanced ID-1A

er verschijnt een serial number; vul dat nummer in op de website

www.trick77.com/tools/mmi3g_vimcode.php

security acces – 16

voer inlogcode in

kies “Do it”

adaptation – 10

channel 48

kies “read”

verander de waarde in “255” (dit is de hoogst mogelijke waarde, betekent dus scherm op zwart bij 255 km/u)

kies “test”

kies “save”

kies “done, go back”

sluit af en herstart MMI met de “Affengriff” = tegelijk indrukken van (1) SETUP (2) grote druk-/draaiknop (3) menutoets rechtsboven

0

255

OK

5. kantelfunctie rechterbuitenspiegel bij inleggen achteruitversnelling

alleen facelift A6

control module 52 = door electronics passengerside

byte 4 (vijfde blokje vanaf rechts, ieder blokje van 2 cijfers is 1 byte, telling begint bij 0)

auto zonder electrisch inklapbare spiegels: verander waarde “40” in “4C”

auto met electrisch inklapbare spiegels: verander waarde “50” in “5C”

bij mij (zonder) was dit 011F02204040410001

en is dit geworden 011F02204C40410001

011C06205040410001

50

5c

011C06205C40410001

6. needle sweep bij starten

alleen facelift A6

controller 17 = instruments

coding

long coding help

byte 1

bit 0 = needle sweep aanvinken

0F74110502000008010100

0FFF110502000008010100

7. waarschuwing als je sleutel in contact laat zitten

alleen facelift A6

controller 17 = instruments

coding

long coding help

byte 1

bit 7 = key warning aanvinken

8. lap timer in boordcomputer (incl. turbodruk en olietemperatuur)

alleen facelift A6

controller 17 = instruments

coding

long coding help

byte 1

bit 3 = lap timer aanvinken

9. acculadingstoestand onder CAR-menu

zowel pré-facelift als facelift A6, verschillen in programmering

In facelift (MMI 3G) aanzetten in hidden menu, nadat je dat hebt vrijgeschakeld.

Open hidden menu

Kies “car”

Kies “cardevextdevicelist”

Vink “Battery” aan

Druk return-knop

Kies “carmenuoperation”

Zet de waarde achter “battery” op 5

Druk return-knop

Druk CAR-knop (sluiten hidden menu)

sluit af en herstart MMI met de “Affengriff” = tegelijk indrukken van (1) SETUP (2) grote druk-/draaiknop (3) menutoets rechtsboven

10. startscherm

zowel pré-facelift als facelift A6, verschillen in programmering

Open hidden menu

Kies “car”

Kies “carcodingvehicle”

Kies “configuration line”

Blader met draaiknop naar instelling die je wilt (S, RS, …), en druk om te bevestigen (keuze “S-line” geeft bij mij geen weergave op display)

Onder “vehicle model line” staat de modelcode (huidige A6 is “C6”), zo kun je in een A6 dus ook RS4 maken…

Druk return-knop

Druk CAR-knop (sluiten hidden menu)

sluit af en herstart MMI met de “Affengriff” = tegelijk indrukken van (1) SETUP (2) grote druk-/draaiknop (3) menutoets rechtsboven

11. lichtsensor: eerder lichten aan

zowel pré-facelift als facelift A6

lichtere ruit programmeren waardoor sensor eerder “schemer” voelt en koplampen eerder aangaan met schakelaar op stand ‘auto’

09 centr. Electronica

Codering regen- lichtsensor

Voorruit 146221 is geworden 150608 (NB: achtergrond van code ken ik niet, is door dealer gedaan met VAS5052)

17 instr. Paneel

App J285

Byte 0

Variant 2 wordt 4

12. hoogte van luchtvering

zowel pré-facelift als facelift A6

Via VagCom kun je het ‘referentieniveau’ van de luchtvering aanpassen om zo de hoogte van de in te stellen niveaus aan te passen. Onderlinge verhoudingen tussen de standen veranderen niet, dynamic blijft “comfort -/- 20mm” bijvoorbeeld.

NB: uit te voeren met draaiende motor en gesloten deuren! (dus laptop buiten auto houden met kabel door geopende ruit…

34 level control

16 security access

code 31564 invoeren “do it!”

10 adaption

kies channel 01 (front left)

WACHT tot de auto zichzelf heeft bewogen naar 2 verschillende niveaus

meet dan de afstand van wielkast (in het midden, op hoogste punt meten) tot middelpunt naaf van de velg in millimeter. als je die waarde invult bij ‘new value’ houdt de auto dezelfde hoogte. als je wilt verlagen, tel je de gewenste verlaging bij de waarde op (dus als je 497mm meet, en je vult 507mm in, zal de auto 10mm worden verlaagd). dus let op, om te verlagen moet je waarde verhogen!

[test]

[save]

en uiteraard zelfde stappen voor channels 02, 03 en 04

daarna channel 05 (confirmation)

[read]

Als de gemeten waarden correct zijn, geef dan waarde = 1 in als new value.

[test]

[save]

tenslotte [done, go back] en klaar.

13. highwaylight en rainlight

ik ken code alleen voor facelift, op pré-fl nooit geprobeerd

let op, rekenmachine met hexadecimaal / decimaal functie nodig!

Uitgaande van lichtschakelaar in stand ‘auto’ en daglicht buiten, kunnen koplampen uit veiligheidsoogpunt toch automatisch worden ontstoken:

Highwaylight: koplampen gaan aan als je enige tijd boven 140km/u rijdt

Rainlight: koplampen gaan aan als ruitenwissers minimaal met een bepaalde frequentie wissen

Stuurgroep 09

coding 07

selecteer regenlichtsensor

zet waarde om naar hexadecimaal

1e en 2e cijfers vormen byte 2

+1 = rainlight

+2 = highwaylight

dus waarde 03 is beide aan

terugzetten naar decimaal en invoeren

00150608

24C50

27C50

00150611

OK

Onderstaand vind je de gegeerde handleiding om uw bluetooth telefoon te activeren in het MMI systeem

Eerst moet je zien dat je het “hidden menu” kan “unlocken” en daar een setting kan wijzigen. Dit doe je als volgt :

1. In VAG-COM/VCDS “Select” aanklikken

2. Module 5F aanklikken (staat onder Tab “Electronics 2”)

3. Vervolgens “Adapation – 10” aanklikken

4. Bij “Channel” tik je 6 in en klik op “Read”

5. Als “New value” tik je 1 in

6. Druk op “Test”

7. Druk op “Save”

8. Druk op “Done, Go Back”

9. Ga volledig uit het programma VAG-COM/VCDS

10. Je moet de MMI niet herstarten, gewoon op CAR + SETUP drukken gedurende 6 seconden en dan gaat het “hidden menu” open

11. In het hidden menu ga je vervolgens naar diagnose>settings>Tel settings misc en je verandert de setting naar [no WLAN/no NAD/BT/HFP] 4/16

12. De microfoon stel je in op 4/6 (zou minimaal 2 moeten zijn voor BT)

13. Je gaat uit het hidden menu met de CAR toets en herstart het MMI-systeem met de volgende combinatie gelijktijdig in te drukken.

Vervolgens koppel je weer de VAGCOM-kabel aan en start je het VAG-COM/VCDS-programma weer op en volg je de volgende stappen :

1. Module 5F aanklikken (staat onder Tab “Electronics 2”)

2. Vervolgens “Adapation – 10” aanklikken

3. Bij “Channel” tik je 17 in en klik op “Read”

4. Als “New value” tik je 1 in (daarmee zet je de Bluetooth functie op “on”, met value 0 staat de Bluetooth functie op “off”)

5. Druk op “Test”

6. Druk op “Save”

7. Druk op “Done, Go Back”

8. Ga volledig uit het programma VAG-COM/VCDS

Nu moet je nog je gsm “inleren” zodat je gsm zichtbaar wordt voor de MMI. Dit kan je nalezen in de handleiding van de MMI. Bij mij ging het als volgt : Bluetooth opzetten op gsm en zien dat hij “zichtbaar” is (ik heb een iPhone). Vervolgens op TEL drukken op de MMI (contact moet opstaan) en de MMI laten zoeken naar BT-apparaten. Voor de rest verwijs ik je liever naar de handleiding van Audi.

(vergeet niet dat je alles op on zet :))