Blog Image

Blog - Dries Willems - Freelance IT Consultant

About the blog

The main reason I use this blog, is to help myself tackling similar issues. You can see this as a very small online documentation library.
Also it is useful for others who experience the same issues.

SCCM 2012 Task Sequence – Install all updates

IT Posted on 12/10/2014 17:34:32

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



How to Update the Surface Pro 3 Firmware Offline using a USB Drive

IT Posted on 12/10/2014 15:00:13

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



Create empty file for unique driver import in SCCM 2012

IT Posted on 12/10/2014 11:27:42

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/



Excluding specific computers from becoming ConfigMgr 2012 clients

IT Posted on 12/07/2014 22:42:27

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/



XCOPY Files / Folder

IT Posted on 11/20/2014 13:11:47

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



Importing Existing Computers into a Device Collection

IT Posted on 11/20/2014 10:30:03

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/



Speed Up SCCM TFTP Performance to PXE clients

IT Posted on 11/20/2014 10:24:29

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



Apply Operation System Failes SCCM 2012 Migration

IT Posted on 10/27/2014 17:13:23

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.



Adobe Reader XI MUI Installation does only install English

IT Posted on 10/17/2014 11:53:23

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.



Disable Java Add-On in Internet Explorer

IT Posted on 09/19/2014 17:28:28

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



Update NTP Server

IT Posted on 09/17/2014 10:57:46

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

net stop w32time

net start w32time

w32tm /resync /rediscover



BMW 130i E87 Hidden Menu

Cars Posted on 09/14/2014 13:55:09

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……



Run VBScripts OSD Task Sequence

IT Posted on 08/13/2014 16:11:23

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



WMI Queries

WQL/WMI Posted on 08/13/2014 16:09:07

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



Install Fonts on Windows 7 OSD Task Sequence

IT Posted on 08/13/2014 16:07:48

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



Transform AD User Group to Device Collection

SCCM Posted on 07/15/2014 14:44:17

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



Disjoin of a domain computer

IT Posted on 06/06/2014 11:38:38

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%



Run CMD within the App-V bubble

IT Posted on 04/22/2014 13:47:19

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



Sequence Visio 2010 with App-V 5.0 SP2

IT Posted on 04/15/2014 14:32:50

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”



Remotely Unpublish and Remove App-V 5.0 Package

IT Posted on 04/14/2014 10:22:32

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\..



Detect Installed KB with Powershell & VBScript for SCCM 2012

IT Posted on 03/24/2014 10:13:57

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



Sort by OS Language

IT Posted on 03/11/2014 11:53:26

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”



Temp

IT Posted on 02/19/2014 14:45:48

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



IE Default Searchprovider

IT Posted on 02/17/2014 13:58:47

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 Application Catalog

IT Posted on 02/13/2014 13:53:50

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).



Deploy printer drivers during ConfigMgr task sequence

IT Posted on 02/12/2014 16:46:07

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



Query OS+Program

IT Posted on 02/05/2014 15:41:11

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”



Application Catalog and Software Center in System Center 2012 Configuration Manager

IT Posted on 02/03/2014 11:45:30

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



SCCM User/System Query

IT Posted on 01/28/2014 16:31:46

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!



SMSTS.LOG

IT Posted on 01/28/2014 12:07:14

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.



Remove Welcome to Google Chrome window

IT Posted on 01/22/2014 16:43:15

[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 …



Enable dotNet 3.5 on Windows 8.1

IT Posted on 10/29/2013 14:54:48

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



When replacing a lcd display for iPhone 4S … the carrier is only showing “Searching”

Problem solver Posted on 01/29/2013 23:57:57

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 😉



Can’t boot from Win7 USB drive on Apple Computer

IT Posted on 12/29/2012 23:50:54

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/



Increase Maximum Kerberos Token Size

IT Posted on 12/03/2012 11:52:07

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



Export Certificate with private key

IT Posted on 02/25/2012 14:37:43

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 😉



The request failed with HTTP status 407

IT Posted on 02/23/2012 16:15:56

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

IT Posted on 02/14/2012 11:52:14

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



Broadcom BCM5709S NetXtreme II GigE iSCSI Adapter Windows 2003 Driver

IT Posted on 02/13/2012 17:05:09

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



LSI Logic Parallel Server 2003 driver

IT Posted on 01/18/2012 15:34:53

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 😉



Install Microsoft Hyper-V Core op USB

IT Posted on 05/31/2011 10:51:27

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



Install driver from cmd dos prompt

IT Posted on 04/27/2011 11:58:02

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

🙂



Vagcom updates for Audi A6 C6 MY2010

Cars Posted on 02/19/2011 20:35:00

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



Enable bluetooth in Audi A4 B8 MY2010

Cars Posted on 02/19/2011 20:11:37

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 :))



« Previous