Showing posts with label OSD. Show all posts
Showing posts with label OSD. Show all posts

Monday, 11 November 2013

MS Güncelleme : SCCM 2012 R2 (OSD, PXE, WDS)

MS'in yayınladığı bu SCCM 2012 R2 güncellemesini özellikle OSD bileşenini ve PXE-enabled dağıtım noktalarını kullanıyorsanız kaçırmamanızı tavsiye ederim. zira WDS ve yavaş imaj transferi problemlerinizin çözümü olabilir.

Don't miss this update for SCCM 2012 R2 if you use OSD feature with PXE-enabled DPs. As it might be your saviour for your WDS or slow transfer problems.

Makaleden alıntı.

Özet


Bu güncelleme Microsoft System Center 2012 R2 Configuration Manager'de aşağıdaki sorunları giderir.

Sorun 1


Bir dağıtım noktasında (Dist. Point) a PXE rolü atadığınızda veya bir boot imajında 'Deploy this boot image from the PXE-enabled distribution point' seçeneğini seçtiğinizde WDS yani Windows Deployment Servisi duruyorsa. Ayrıca Windows Uygulama günlüğünde aşağıdaki hatasının alınması.

Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0xae4
Faulting application start time: 0x01cec5d767184634
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll

Not Bu problem sadece site sucnularındaki dağıtım noktalarını etkiler.

Sorun 2


İşletim sistemi imajının SCCM 2012 R2 istemcisine indirilme işlemi daha eski versiyona sahip SCCM 2012 istemcilerinden uzun sürüyor olması.

Kurulum


Bu güncelleme Central Admin. ve Primary sitelara, yönetim konsollarına ve istemcilere uygulanır. Site sunucusuna kurduğunuzda size istemci güncelleme paketi oluşturma imkanı da sunar.

Site sunucularına kurulumdan sonra boot imajlarının update edilmesi gerektiğini unutmayın.

Tam makaleye http://support.microsoft.com/kb/2905002 adresinden ulaşabilirsiniz.

 

MS Update for SCCM 2012 R2 (OSD, PXE, WDS)

Don't miss this update for SCCM 2012 R2 if you use OSD feature with PXE-enabled DPs. As it might be your saviour for your WDS or slow transfer problems.

Excerpt from the article.

Summary


This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.

Issue 1


After you enable the PXE Service Point role on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running. Additionally, entries that resemble the following are logged in the Windows Application log:


Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0xae4
Faulting application start time: 0x01cec5d767184634
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll


Note This problem affects only distribution points that are installed on site servers.

Issue 2


When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behaviour when the target client is running Windows PE or a full Windows operating system.

Installation information


This update applies to Central Administration sites, primary sites, administrator consoles, and clients. Applying this update to a site server will let you create client update packages.

After the update is installed on site servers, any operating system boot images should be updated.
Notes


  • All existing media (such as stand-alone, boot, or prestaged) that use existing boot images (default or custom) will have to be re-created.

  • To fully fix the problem in Issue 2, the client side .msp file has to be installed during the "Setup Windows and ConfigMgr task by using the PATCH= command.


Full article can be reached at http://support.microsoft.com/kb/2905002

 

Monday, 7 January 2013

SCCM'de MDT DB kullanarak domaine dahil etme islemini otomatik ve lokasyon spesifik gerceklestirmek

Eger sizde benim gibi Task Sequence'nizde bilgisayarlarin domaine dahil olma isleminde "Apply Network Settings" lokasyona ozel degerleri otomatik algilayip uygulamak istiyorsaniz. Yani bir den fazla domain'e sahipseniz ancak bir den fazla islem yaratip her bir domain icin ayri sorgular yazmak istemiyorsaniz. SCCM'nize entegre olmus MDT'nin veritabanini kullanarak bu islemi kolaylastirabilirsiniz.

Tek yapmaniz gereken MDT DB de yaratiiginiz lokasyonlarin ozelliklerine gerekli degerleri girmek ve SCCM OSD'de ki Task Sequence'de bu degerleri cagirmak olacak.

MDT DB'de lokasyon altinda degistirilecek degerler Domain and Workgroup bolumu altinda yer almakta, buradaki degerleri kendi domain ayarlariniza gore konfigure etmeniz gerekmekte. Bu zaten sadece MDT kullanilarak yapilan isletim sistemi kurulumlarindan bildiginiz bir adim olabilir.

07-01-2013 13-27-03






















DomainAdmin : 
Bilgisayari domaine eklerken kullanilacak kullanici adi. Ornek : OSDAdmin
DomainAdminDomain : DomainAdmin kullanicisinin domaini Ornek: Domain1
DomainAdminPassword : Domain Admin kullanicisinin sifresi
JoinDomain : Bilgisayarin dahil edilecegi domain adi, Ornek: Domain1.yerel
MachineObjectOU : Bilgisayar objesinin yaratilacagi OU, Ornek: OU=YeniBilgisayarlar,DC=Domain1,DC=yerel

Daha sonra SCCM'de ki mevcut task sequence'nizde Apply Network Settings adimini konfigure etmeniz gerekmekte, degisken isimleri aynen MDT DB deki gibi olacagindan isiniz cok basit.

Domain : %JoinDomain%
DomainOU : %MachineObjectOU%
Account : %DomainAdmin%
Password : %DomainAdminPassword%
07-01-2013 13-25-08

Seklinde degisikliklerinizi yapmaniz yeterli olacak, sifre yi girerken yuzdeleri basa ve sona yazmayi unutmayin,

Using MDT DB to get location specific Domain Joining parameters in SCCM OSD

If you have multiple domains as me and want to automate domain joining task by sensing locations automatically in SCCM OSD, you can use MDT DB to do it easily. You can also do this by adding more actions with different queries to your TS or customizing your coustomsettings.ini. But I prefer using MDT DB as changes there doesn't need to be refresh as packages, GUI makes it easier to manage and more foolproof, etc.

All you need to do is modifying location details on your MDT DB and call these variables in your SCCM TS.

So first edit your location details in MDT Workbench, you'll need to edit four values here as shown below.

07-01-2013 13-27-03






















DomainAdmin :
The name of the account used to join the domain. Example : OSDAdmin
DomainAdminDomain : The domain of the account used to join the domain. Example: Domain1
DomainAdminPassword : The password of the account used to join the domain.
JoinDomain : The name of the domain in which the computer should be placed. Example: Domain1.local
MachineObjectOU : The OU in which the computer account should be created (if it does not already exist)., Exaple: OU=NewComps,DC=Domain1,DC=Local

Then you'll need to modify your "Apply Network Settings" action in your TS to use values in MDT DB. It is very as MDT Workbench displays these as it is. So all you need to do adding % to the start and the end of the variable as below.

Domain : %JoinDomain%
DomainOU : %MachineObjectOU%
Account : %DomainAdmin%
Password : %DomainAdminPassword%
 07-01-2013 13-25-08

All done, now you can test it.

Please note that you'll need a working SCCM and MDT integration to use this method first.

Thursday, 6 December 2012

How to prompt for computer name in MDT/SCCM Task Sequence (OSD)

I was using Collection Variables in Collection Settings to ask Computer Name [OSDComputerName] at the beginning of my OSD Task Sequences. It was useful but it doesn't have confirmation or correction features.

So I wanted to change it to something asks if the entered computer names is correct and allow user to change name before final confirmation.

And it worked nicely : )

My new prompt for the computer name script is
gfdgdfgdgdgdg

Feel free to use, change or optimize.

You can create a SCCM Package and run this script via "Run Command Line" action in your task sequence (cscript "PromptForComputerName.wsf").

Or you can place it into your MDT Scripts (Toolkit package) and  run "Use Toolkit Package" action before it from, then run (cscript "%deployroot%PersonalPromptForComputerName.wsf") in a "Run Command Line" action just after "Use Toolkit Package".

Friday, 30 November 2012

MDT/SCCM OSD Task Sequence - Install Software Failed (hr=80008013) for Programs with dependencies


When you install an application with dependencies (nested); by running other SCCM package/programs first in MDT/SCCM OSD it fails with the error code  0x80008013 which means (E_FAIL_DEPENDENCY_NOT_RUN : This program cannot run because it depends on another program that has not run successfully before. This error code is returned to task sequence manager when a task sequence Install Software Action step cannot be run because the step has a child program which has not been run before.).

The reason is OSD in SCCM can't install the dependencies first, so you need to separate programs for your OSD Install software tasks.

The task sequence execution engine failed executing the action (Cisco Any Connect) in the group (Laptop Software) with the error code 2147516435 Action output: _ProgramID="Silent  Install",PKG_PackageID="SMS0012C"' Verified policy is compiled in 'root\ccm\policy\machine' namespace content location count = 1 Invoking Execution Manager to install software
FALSE, HRESULT=80008013 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,282)
0, HRESULT=80008013 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,746)
Entering ReleaseSource() for \\DPSERVER\SMSPKGE$\SMS0012C reference count 1 for the source \\DPSERVER\SMSPKGE$\SMS0012C\ before releasing
Released the resolved source \\DPSERVER\SMSPKGE$\SMS0012CpInstall->Install(sPackageID, sProgramName), HRESULT=80008013 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374)
Failed to invoke Execution Manager to Install Software for PackageID='SMS0012C' ProgramID='Silent Install' AdvertID='SMS20333' hr=0x80008013 Install Software failed, hr=0x80008013 Install Software failed, hr=0x80008013.

See http://technet.microsoft.com/en-us/library/bb632794.aspx  for
Custom Error Codes for Configuration Manager 2007.



Thursday, 29 November 2012

MDT / SCCM OSD - Run actions based on chassis type

It is very easy to run chassis type specific actions in task sequences by querying , all you need to do is adding  Task Sequence Variable in Options. Fill Variable field with IsLaptop , select your condition and write the value you wanted (True or False)
30-11-2012 12-48-15

 

Monday, 26 November 2012

WinPE AdoDB SQL Connection Error (429)

I was using MDT wDB for OS deployments, now I am creating the same (better) system with SCCM for wider and easier deployment. I prefer MDT integration to SCCM as it provides lots of flexibility and customizability.

Today, I wanted to use MDT DB with my SCCM OSD, so I created a new MDT Settings package and copied my old CustomSettings.ini from MDT and customized. Duplicated my current build TS and changed the MDT Settings package in respective Gather actions.

Deployed a test machine and found out no localization settings have applied. So I found the error "Unable to create ADODB.Connection object, impossible to query SQL Server: ActiveX component can't create object ( 429 )" in logs. After a few web search I found MDT Boot image usage is recommended as it has necessary libraries to create ADODB connection.

As usual I wanted to fix that instead of using my old MDT boot image, checked WinPE_FPs folder in WAIK and seen there is a winpe-mdac.cab (MS Data Access Components) and added this package to boot image.

  • dism /mount-wim /WimFile:g:\wimwork\boot.csrx64.wim /index:1 /MountDir:G:\WimWork\x64

  • dism /image:G:\WIMWork\csrx64 /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-mdac.cab"

  • dism /unmount-image /MountDir:G:\WIMWork\csrx64 /Commit


Now I have necessary libraries in my new boot image and it can connect to SQL server.

Note : Don't forget to change Netlib value to DBMSSOCN in your CustomSettings.ini if you will use SQL Authentication instead of Windows Authentication.

Thursday, 22 November 2012

Configuring location based settings automatically by using Win32 IP4RouteTable in OSD - Task Sequence

The idea was creating location specific variable sets to automatically configure regional settings during deployment.

1  2

 
Select * FROM Win32_IP4RouteTable WHERE Destination='0.0.0.0' AND ( NextHop='10.99.0.254' OR NextHop='10.101.0.254' OR NextHop='10.103.0.254' OR NextHop='10.104.0.254' )

The query above is very useful as it queries the routing table to find gateway and it looks ok when you run test it in SCCM Console.

But, it doesn’t work and generates errors below during deployment

(You can use VB, PS scripts, Control.exe with .xml file or other methods by using same WMI query after Setup Windows & CM action (Windows Mode) to set regional settings, they should be easier. But I wondered if I can fix that one, as I always have used default boot images provided in WAIK and I wanted to gain some familiarity with WinPE imaging/tools. I am sure the method below may not be the good/best practise but that is what I did in last few hours, it was good experimental work for me and I believe some parts can be useful for others as well.)

Windows could not parse or process the unattended answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].

 3
If you click ok to Restart/OK, it goes in to reboot loop with message below.The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the
installation.

4

And also the error message below can be found in advertisement status messages.

5

If you check sms*.log files in deployment client drive you can also find error messages related to operands. (Attaching .vhd is very useful to do that.)
Reason ? The reason is Win32_IP4RouteTable class is invalid as it is not included in winpe-wmi.cab.

6
Win32_IP4RouteTable class has two files named Wmipiprt.mof and Wmipiprt.dll

(For more details : http://msdn.microsoft.com/en-gb/library/windows/desktop/aa394162(v=vs.85).aspx)
So I wanted to include this class to my Win-PE image.

 

1. Preperation

Enable command support option in your current boot image, start deployment but don’t select TS and proceed to installation.

7

Press F8 to open command prompt

  1. Connect to your workstation

    • (net use K: \yourmachinec$ )



  2. Copy the wmipiprt.* files to WindowsSystem32wbem folder (X: Drive)

    • (Copy K:windowssystem32wbemwmipiprt.* X:WindowsSystem32wbem)



  3. Change your working folder to X:WindowsSystem32wbem

    • Cd X:WindowsSystem32wbem



  4. Run MOF compiler for the class

    • Mofcomp wmipiprt.mof



  5. Take a copy of Win-PE Wbem

    • Xcopy X:WindowsSystem32wbem K:WinpeWork /s /e



  6. Register the the dll

    • Regsvr32 wmipiprt.dll



  7. Backup Win-PE HKLMSoftware (If you are ok the .reg file I provided you can skip all reg steps until Modifying the Image)

    • Reg save HKLMSOFTWARE HKLMSoft.reg



  8. Take a copy of exported reg file

    • Copy HKLMSoft.reg K:WinpeWork




On your workstation

Load the C:WinpeworkHKLMSoft.reg file with load hive option to your workstations HKLM, you can use any name for Hive name (e.g. WINPE)

8

Then search wmipiprt in loaded hive,


You’ll find two entries under CLSID, export these to .reg files and merge in one reg file. And unload the hive “WINPE”.  (You can also use the .reg below)
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\WIMSOFT\Classes\CLSID\{23B77E99-5C2D-482D-A795-62CA3AE5B673}]
@="WBEM IP Route Provider"

[HKEY_LOCAL_MACHINE\WIMSOFT\Classes\CLSID\{23B77E99-5C2D-482D-A795-62CA3AE5B673}\InprocServer32]
@="X:\\Windows\\System32\\wbem\\WMIPIPRT.dll"
"ThreadingModel"="Both"

[HKEY_LOCAL_MACHINE\WIMSOFT\Classes\CLSID\{6D7A4B0E-66D5-4AC3-A7ED-0189E8CF5E77}]
@="WBEM IP Route Event Provider"

[HKEY_LOCAL_MACHINE\WIMSOFT\Classes\CLSID\{6D7A4B0E-66D5-4AC3-A7ED-0189E8CF5E77}\InprocServer32]
@="X:\\Windows\\System32\\wbem\\WMIPIPRT.dll"
"ThreadingModel"="Both"


2. Modifying the image (Be sure you have a backup of your original boot image in separate place.)

Mount your boot image in writable mode.

Imagex /mountrw G:WIMWorkx64boot.wim G:WIMWorkx64mount


(G:WIMWorkx64mount is an empty folder)


Open G:WIMWorkx64mount folder, you’ll see your winpe image contents

Delete G:WIMWorkx64mountWindowsSystem32wbem contents

Copy the K:WinpeWorkwbem content you have copied from running Win-PE to your work folder in first steps of Preparation above.

Run Regedit, select HKLM then select load hive from menu,

Select G:WIMWorkx64mountWindowsSystem32ConfigSoftware to load and give WIMSOFT as a name if you are going to use my .reg file above.


Run the .reg you’ve created by correcting paths or directly the one above.

(Check two new entries under WIMSOFTClassesCLSID)


Unload WIMSOFT Hive.

Now we need to dismount the image with commit option.

Imagex /unmount /commit G:WIMWorkx64mount


Finished.

Take a backup of your current boot image on SCCM, copy this one to your source and update your distribution points to test. (Or create a new image, to test first.)

10

Now you can use Win32_IP4RoutingTable in Win-PE mode.

Place your variable set tasks just before the Configure action in PostInstall phase.

Saturday, 20 August 2011

Reset Windows Update Agent variables via sysprep

Open you sysprep.inf file with notepad and add lines below under [GuiRunOnce], if you don't have [GuiRunOnce] you can create it. If you have already command under this section you should re-number commands below like Command6.../

This will run the commands below once at system startup after image applied and delete previous entries from the image you have taken, and the agent will re-generate new SusClientId for you.
Command0="reg.exe delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f"
Command1="reg.exe delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f"
Command2="reg.exe delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f"
Command3="reg.exe delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIDValidation /f"

Tuesday, 9 August 2011

WDS BINLSVC 0x5 525 - Pending Device Approve ederken Access Denied hatasi almak

Merhaba WDS (Windows Deployment Service) kullanarak isletim sistemi kurmaya calistiginiz da istek onaylama asamasina geldiginizde karsilasabileceginiz bir sorunun cozumune deginmek istedim. Aslinda asagidaki bilgiler sorun cozumunden ziyade WDS i yapilandirirken dikkat etmeniz gereken bir ayar olarak da kategorize edilebilir. PXEBoot araciligi ile istemciyi baslattiginizda DHCP den IP almasi, DHCP serverdan PXEBoot sunucusunu ve bootfile adini almasi ardindan WDS ile ile irtibata gectiginde WDS ayarlamis oldugunuz PXE Response settings e gore istemciye yanit verir , kurulabilecek veya calistirilabilecek imajlari listelemeden once, otomatik yanitlamaya ayarladi iseniz bekleme den yani pending devices listesine dusmeden bir sonraki ekrana gecer veya onay gerektirdiyseniz pending device listesine duser ancak her iki sekildede Directory Services tab inda da ayarlayabildiginiz OU altina Computer Object sini yaratmaya calistiginda gerekli ayari yapmadiysaniz Access Denied hatasi alirsiniz device i onaylarken. Ve Event Viewer da asagida gordugunuz hata ile karsilasirsiniz.

WDSApprove (9)

Hatanin sebebi aslinda oldukca acik sekilde hata kaydinda da yer alir, eger bilgisayar isimlendirme policylerine takilmiyorsaniz , icinde computer objesi yaratmaya calistiginiz OU altinda WDS inizin calistigi sunucunun nesne yaratma hakki yoktur, bu hakki sunucunuza atamak icin. Active Directory Users and Computers aracini calistirip hak tanimlamasi yapmaniz gerekecek bu sebeble Domain Admins grubuna dahil kullaniciniz ile araci acip WDS de Directory Services da belirttiginiz veya sectiginiz OU nun uzerine sag tusla basarak Delegate Control u seciniz.

WDSApprove

Gelen ekranda Add tusuna basiniz

WDSApprove (2)

Object Types i secerek Computers i filtrenize ekleyiniz , cunku Computer Accountu ekleyecegiz.

WDSApprove (3)

WDS sunucunuzun ismini yazip arattirdiktan sonra islemi onaylayiniz.

WDSApprove (4)

Tasks to delegate ekraninda Create a custom task to delegate secenegini seciniz ve sonraki ekrana geciniz.

WDSApprove (5)

AD Object Type ekraninda Only the following objects in folder secenegini secerek verecegimiz hakkin sinirlarini daraltalim ve listeden Computer Objects i secelim ve create selected objects in this folder ile bu haklari yaratacagimizi belirtelim ve sonraki adima gecelim.

WDSApprove (6)

Gelecek olan Permissions ekraninda ise Write All Properties secenegini secerek verecegimiz hakkin sadece yazma ile ilgili olmasini belirleyelim ve sonraki adima gecip islemimizi tamamlayalim.

WDSApprove (7)

Vermek uzere oldugumuz haklarla ilgili ozet bilgileri gozden gecirip islemin tamamlanmasini onaylayalim.

WDSApprove (8)

Saturday, 6 August 2011

WDS'te boot menüyü configure etme

Windows Deployment Services boot menusu bir den falza boot image e sahipseniz konfigure edilir , menuyu konfigure etmek iste asagidakilerden birini yapabilirsiniz.

  1. Farkli mimaride bir den fazla Window PE imajini yukleyebilirsiniz,

  2. Ayni mimaride iki veya daha fazla Windows PE imajini yukleyebilirsiniz,

  3. WDSUtil i kullanabilirsiniz, WDSUtil i nasil kullanacaginiz ve parametretlerini gormek icin /? seklinde calistirmaniz yeterli olacaktir.


Biz simdi grafik arayuzden boot imaji eklemeye degil de komut satirindan nasil ekleyebiliyoruz ona bakacagiz.

Komut satirinda imajiniza ait tam yolu imajinizin ismi dahil yazmaya dikkat ediniz, ornegin;

WDSUTIL /add-image /imagefile:\\sunucu\paylasim\imajlarim\imajdosyasi /imagetype:boot

yukarida da gordugunuz gibi add-image parametresi ile imaji eklemek istedigimizi, imagefile ile imajimizin adresiniz , imagetype ile ise imajimizin tipini yani boot imaji oldugunu belirtiyoruz.

Simdi istemcinizi yeniden baslattiginizda boot menusunde yeni eklediginiz imaji da gorebileceksiniz, normalde sadece standart bir imajiniz vardi ise artik menuyu gorebiliyor olmaniz gerekir.

Friday, 22 July 2011

MDT Paylaşım Lokasyonunu Otomatik Belirleme

MDT ile imaj olusturmaya baslayali uzun zaman oldu, simdi farkli lokasyonlardan da tek imaj , tek veritabani, tek paylasim kullanabilmek icin uzerinde calismaktayim, her lokasyonun kendi lokalinden kaynaklara ulasabilmesi icin SQL Replikasyonu, DFS-R gibi teknolojilerden faydalanmaktayim. Ancak dun DFS performansindan veya olasi DFS problemlerine karsin bu is baska nasil yapilir diye dokumanlari okurken BootStrap.ini de Gateway tanimlamalari ile lokasyon tanimlanabildigini buldum, bu ozellik cok hos , istemci gatewayinden nerede oldugunu ayirt edebilip ayarlari buna gore ozellestirebiliyorsunuz. Ankara'da isen Ankara paylasimina eris, su kullanici ile diyebiliyorsunuz.

Veya DeployRoot u tamamen bos birakabiliyorsunuz bu durumda sistem sizin yarattiginiz LocationServer.xml dosyasini okuyor ve kullaniciniza sizin tanimlamis oldugunu lokasyonlari listeliyor, bu yontemle ayni lokasyonda bir den fazla paylasiminiz var ise bunlara agirlik vererek yuku de dagitabiliyorsunuz.

Ben hem bootstrap.ini de gateway ve lokasyon degiskenlerini kullandim hem de eger lokasyonlardan birine eslesmedigi durumda LocationServer.xml i kullanmasi icin konfigure ettim.

BootStrap.ini de yapmaniz gereken

[Settings] altinda Priority i degistirmeniz olacak, boylelikle islem once Gateway eslesmelerine oncelik verecek ornegin :

[Settings]
Priority=DefaultGateway,Default

Daha sonra gatewayleri ve lokasyonlari tanimlayacaksiniz, ornegin

[Default Gateway]
192.168.1.1=Istanbul
192.168.3.1=Ankara

Daha sonra lokasyona ait ozellikleri asagidaki sekilde tanimlayabilirsiniz.

[Istanbul]
DeployRoot=\IstanbulSunucunuzDeploymentShare$ (MDT2010 oncesinde Distribution$)

[Ankara]
DeployRoot=\AnkaraSunucunuzDeploymentShare$ (MDT2010 oncesinde Distribution$)

Ikinci oncelik ise varsayilan yani Default, bu eslesme olmamasinda kullanicak ana yontem

[Default]

Buraya eslesme olmazsa kullansin diye bir sunucu tanimlabilirsiniz veya bos birakip sistemin LocationServer.xml okumasini isteyebilirsiniz.

Yukaridaki bolge degiskenlerine elbette normalde kullanabildiginiz UserID, UserDomain, SkipBDDWelcome vs gibi degerleri kullanabilirsiniz.

LocationServer.xml i yaratmak icin MDT dokumanini incelemeniz gerekiyor cunku kurulum klasorlerinde bulamayacaksiniz. Ben burada bir ornegi sizinle paylasacagim

2009-10-01 15.00-01
Ornegin yukaridaki gibi bir XML i yaratip Disk:DeploymentShareExtra FilesDeployControl altina kopyalayip imaji tekrar olusturursaniz boot sirasinda eger herhangi bir deployroot tanimi bulunamaz ise sistem size xml de tanimlamis oldugunuz sunuculari listeleyecektir. Extra Files klasorunu MDT de Share ozelliklerine Extra Files kismindan tanimlamalisiniz ki dosyayi imaj icina alsin, bunu atlamayiniz.

Ayni XML de bolgeye has ozellikleri de tanimlayabilirsiniz , ornegin alan kodu icin

2009-10-01 15.03-02

Fakat da bootstrap.ini de oldugu gibi paylasima erisecek kullanici tanimlanamamakta, bunun olmamasi benim planlarimi aksatmisti cunku yarattigim imajlar kurulumcuya sadece makine adi sormaya ayarli, geri kalan tum bilgileri klavye, alan kodu, domain, ou, uygulamalar vb seyleri zaten otomatize etmistim. Bunun uzerine MDT scriptleri nasil calisir diye arastirmaya basladim ve benim isimi gorecek bir cozum buldum, ayni seye ihtiyaci olacaklar icin umarim faydali olur.

ScriptsDeployWiz_Validation.vbs dosyasinda asagidaki kismi bulun
ValidateDeployRoot = FALSE

Do
On Error Resume Next
Err.Clear
If oFSO.FileExists(DeployRoot.value & "ControlOperatingSystems.xml" ) then

ve su sekilde eklemeyi yapin, normalde asagidaki ek daha alt satirlarda zaten degiskenleri okumak icin var ancak bu kod kullanici haklari size sorulduktan sonra calistigi icin, kullanici bilgileri icin kullanilamamakta, biz kullanici haklari kismindan once okuyacagiz parametrelerimizi,

ValidateDeployRoot = FALSE
For each oItem in oXMLSiteData.selectNodes("//servers/server")
If SiteList.value = oUtility.SelectSingleNodeString(oItem,"serverid") then
For each oVariable in oItem.selectNodes("otherparameters/parameter")
Set oName = oVariable.Attributes.getQualifiedItem("name","")
If not oName is Nothing then
oProperties(oName.Value) = oVariable.Text
End if
Next

End if
Next
Do
On Error Resume Next
Err.Clear
If oFSO.FileExists(DeployRoot.value & "ControlOperatingSystems.xml" ) then

Daha sonra asagidaki bolumu

oEnvironment.Item("UserID") = ""
oEnvironment.Item("UserDomain") = ""
oEnvironment.Item("UserPassword") = ""

su sekilde degistirin ki , XML den okudugumuz bilgileri eslestirelim,

oEnvironment.Item("UserID") = oProperties("UserID")
oEnvironment.Item("UserDomain") = oProperties("UserDomain")
oEnvironment.Item("UserPassword") = oProperties("UserPassword")

Asagidakileri de yukarida verilen ornekteki gibi parametrelere ekleyiniz.

2009-10-01 15.13-03

Imajinizi olusturup , boot ettiginiz de eger GW eslesmesi olmazsa veya bootstrap.ini de DeployRoot tanimli degilse sistem size bolge-sunucu listesini gosterecektir, ve siz secim yapip Next'e bastiginizda kullanici bilgileri ekrani doldurulmus gelecektir.

Iyi gunler.

Not:XML leri imaj seklinde koydum cunku blogger xml leri algilayip sadece atanmis degerleri gosteriyordu.

(MDT Paylaşım Lokasyonunu Otomatik Belirleme)

Saturday, 22 January 2011

Unattended.txt (GuiUnttended) TimeZone Endeksi

Asagida Unattended.txt dosyasini duzenlerken TimeZone degeri vermek icin ihtiyac duyabileceginiz TimeZone index ini bulabilirsiniz arkadaslar, GUIUnattended bolumu altinda bulunan TimeZone icin degeri TimeZone=130 (Istanbul icin) seklinde verebilirsiniz.


IndexTime ZoneDescription
000Dateline Standard Time(GMT-12:00) International Date Line West
001Samoa Standard Time(GMT-11:00) Midway Island, Samoa
002Hawaiian Standard Time(GMT-10:00) Hawaii
003Alaskan Standard Time(GMT-09:00) Alaska
004Pacific Standard Time(GMT-08:00) Pacific Time (US and Canada); Tijuana
010Mountain Standard Time(GMT-07:00) Mountain Time (US and Canada)
013Mexico Standard Time 2(GMT-07:00) Chihuahua, La Paz, Mazatlan
015U.S. Mountain Standard Time(GMT-07:00) Arizona
020Central Standard Time(GMT-06:00) Central Time (US and Canada)
025Canada Central Standard Time(GMT-06:00) Saskatchewan
030Mexico Standard Time(GMT-06:00) Guadalajara, Mexico City, Monterrey
033Central America Standard Time(GMT-06:00) Central America
035Eastern Standard Time(GMT-05:00) Eastern Time (US and Canada)
040U.S. Eastern Standard Time(GMT-05:00) Indiana (East)
045S.A. Pacific Standard Time(GMT-05:00) Bogota, Lima, Quito
050Atlantic Standard Time(GMT-04:00) Atlantic Time (Canada)
055S.A. Western Standard Time(GMT-04:00) Caracas, La Paz
056Pacific S.A. Standard Time(GMT-04:00) Santiago
060Newfoundland and Labrador Standard Time(GMT-03:30) Newfoundland and Labrador
065E. South America Standard Time(GMT-03:00) Brasilia
070S.A. Eastern Standard Time(GMT-03:00) Buenos Aires, Georgetown
073Greenland Standard Time(GMT-03:00) Greenland
075Mid-Atlantic Standard Time(GMT-02:00) Mid-Atlantic
080Azores Standard Time(GMT-01:00) Azores
083Cape Verde Standard Time(GMT-01:00) Cape Verde Islands
085GMT Standard Time(GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
090Greenwich Standard Time(GMT) Casablanca, Monrovia
095Central Europe Standard Time(GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague
100Central European Standard Time(GMT+01:00) Sarajevo, Skopje, Warsaw, Zagreb
105Romance Standard Time(GMT+01:00) Brussels, Copenhagen, Madrid, Paris
110W. Europe Standard Time(GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
113W. Central Africa Standard Time(GMT+01:00) West Central Africa
115E. Europe Standard Time(GMT+02:00) Bucharest
120Egypt Standard Time(GMT+02:00) Cairo
125FLE Standard Time(GMT+02:00) Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius
130GTB Standard Time(GMT+02:00) Athens, Istanbul, Minsk
135Israel Standard Time(GMT+02:00) Jerusalem
140South Africa Standard Time(GMT+02:00) Harare, Pretoria
145Russian Standard Time(GMT+03:00) Moscow, St. Petersburg, Volgograd
150Arab Standard Time(GMT+03:00) Kuwait, Riyadh
155E. Africa Standard Time(GMT+03:00) Nairobi
158Arabic Standard Time(GMT+03:00) Baghdad
160Iran Standard Time(GMT+03:30) Tehran
165Arabian Standard Time(GMT+04:00) Abu Dhabi, Muscat
170Caucasus Standard Time(GMT+04:00) Baku, Tbilisi, Yerevan
175Transitional Islamic State of Afghanistan Std.
(GMT+04:30) Kabul
180Ekaterinburg Standard Time(GMT+05:00) Ekaterinburg
185West Asia Standard Time(GMT+05:00) Islamabad, Karachi, Tashkent
190India Standard Time(GMT+05:30) Chennai, Kolkata, Mumbai, New Delhi
193Nepal Standard Time(GMT+05:45) Kathmandu
195Central Asia Standard Time(GMT+06:00) Astana, Dhaka
200Sri Lanka Standard Time(GMT+06:00) Sri Jayawardenepura
201N. Central Asia Standard Time(GMT+06:00) Almaty, Novosibirsk
203Myanmar Standard Time(GMT+06:30) Yangon (Rangoon)
205S.E. Asia Standard Time(GMT+07:00) Bangkok, Hanoi, Jakarta
207North Asia Standard Time(GMT+07:00) Krasnoyarsk
210China Standard Time(GMT+08:00) Beijing, Chongqing, Hong Kong SAR, Urumqi
215Singapore Standard Time(GMT+08:00) Kuala Lumpur, Singapore
220Taipei Standard Time(GMT+08:00) Taipei
225W. Australia Standard Time(GMT+08:00) Perth
227North Asia East Standard Time(GMT+08:00) Irkutsk, Ulaan Bataar
230Korea Standard Time(GMT+09:00) Seoul
235Tokyo Standard Time(GMT+09:00) Osaka, Sapporo, Tokyo
240Yakutsk Standard Time(GMT+09:00) Yakutsk
245A.U.S. Central Standard Time(GMT+09:30) Darwin
250Cen. Australia Standard Time(GMT+09:30) Adelaide
255A.U.S. Eastern Standard Time(GMT+10:00) Canberra, Melbourne, Sydney
260E. Australia Standard Time(GMT+10:00) Brisbane
265Tasmania Standard Time(GMT+10:00) Hobart
270Vladivostok Standard Time(GMT+10:00) Vladivostok
275West Pacific Standard Time(GMT+10:00) Guam, Port Moresby
280Central Pacific Standard Time(GMT+11:00) Magadan, Solomon Islands, New Caledonia
285Fiji Islands Standard Time(GMT+12:00) Fiji Islands, Kamchatka, Marshall Islands
290New Zealand Standard Time(GMT+12:00) Auckland, Wellington
300Tonga Standard Time(GMT+13:00) Nuku'alofa

Sunday, 15 August 2010

SMS/SCCM de Notebooklari filtrelemek

Merhaba, uzerinde calistigim deployment projesinde az once ihtiyacim olunca buldugum bilgileri sizlerle paylasmak istedim, yeni kurulmus tum sistemlerin icinde diz ustu bilgisayarlari filtreleyip yeni bir collection yaratma ihtiyacim dogdu VPN clientlari otomatik yayabilmek icin, bunun icinde mevcut collection icinde kasa tipine gore filtrelemek aklima geldi, ancak SMS/SCCM de System Enclosure altindaki Chassis Type lar isimleri ile degilde asagidaki sekilde degerleri karsiligi rakamlar ile belirtildiginden degerlerin neye denk geldigini bulmam gerekti dogal olarak, burada bulunan degerler icin Microsoft'un hazirladigi listeye Identifying the Chassis Type of a Computer adresinden ulasabilirsiniz, nedir bilmiyorum ama listede Pizza Box, Lunch Box gibi degisik tiplere de rastlamak mumkun :) .

Degeri Tipi
1 Other
2 Unknown
3 Desktop
4 Low Profile Desktop
5 Pizza Box
6 Mini Tower
7 Tower
8 Portable
9 Laptop
10 Notebook
11 Hand Held
12 Docking Station
13 All in One
14 Sub Notebook
15 Space-Saving
16 Lunch Box
17 Main System Chassis
18 Expansion Chassis
19 Sub Chassis
20 Bus Expansion Chassis
21 Peripheral Chassis
22 Storage Chassis
23 Rack Mount Chassis
24 Sealed-Case PC

NotebooksFilter-1

Tuesday, 4 May 2010

Unattended.txt icin Keyboard Layout Listesi

Bana BDD/MDT de Windows XP Build ozelliklerini konfigure etmek icin Unattended.txt i duzenlerken lazim oldu, sizlerlede asagidaki listeyi paylasmak istedim.

["Keyboard Layout"]
0000041C = "Albanian"
00000423 = "Belarusian"
00000813 = "Belgian Dutch"
0000080C = "Belgian French"
00000416 = "Brazilian (ABNT)"
00000402 = "Bulgarian"
00010402 = "Bulgarian Latin"
00001009 = "Canadian English (Multilingual)"
00000C0C = "Canadian French"
00010C0C = "Canadian French (Multilingual)"
0000041a = "Croatian"
00000405 = "Czech"
00010405 = "Czech (QWERTY)"
00000406 = "Danish"
00000413 = "Dutch"
00000425 = "Estonian"
0000040B = "Finnish"
0000040C = "French"
00000407 = "German"
00010407 = "German (IBM)"
00000408 = "Greek"
00050408 = "Greek Latin"
00010408 = "Greek (220)"
00030408 = "Greek (220) Latin"
00020408 = "Greek (319)"
00040408 = "Greek (319) Latin"
0000040E = "Hungarian"
0001040E = "Hungarian 101-key"
0000040F = "Icelandic"
00001809 = "Irish"
00000410 = "Italian"
00010410 = "Italian (142)"
0000080A = "Latin American"
00000426 = "Latvian"
00010426 = "Latvian (QWERTY)"
00000427 = "Lithuanian"
00000414 = "Norwegian"
00000415 = "Polish (Programmers)"
00010415 = "Polish (214)"
00000816 = "Portuguese"
00000418 = "Romanian"
00000419 = "Russian"
00010419 = "Russian (Typewriter)"
00000C1A = "Serbian Cyrillic"
00010C1A = "Serbian Latin"
0000041B = "Slovak"
0001041B = "Slovak (QWERTY)"
00000424 = "Slovenian"
0000040A = "Spanish"
0001040A = "Spanish variation"
0000041D = "Swedish"
0000100C = "Swiss French"
00000807 = "Swiss German"
0001041F = "Turkish F"
0000041F = "Turkish Q"
00000422 = "Ukrainian"
00000809 = "United Kingdom"
00000409 = "US"
00010409 = "US-Dvorak"
00030409 = "US-Dvorak for left hand"
00040409 = "US-Dvorak for right hand"
00020409 = "US-International"

 

Tuesday, 5 February 2008

Keyboard Layout values for Unattended installations

I have just needed the list below to customize my Windows XP Build in BDD, so I am sharing the list because I couldn't found the list quickly enough, I have extracted list from TXTSetup.SIF file.

["Keyboard Layout"]
0000041C = "Albanian"
00000423 = "Belarusian"
00000813 = "Belgian Dutch"
0000080C = "Belgian French"
00000416 = "Brazilian (ABNT)"
00000402 = "Bulgarian"
00010402 = "Bulgarian Latin"
00001009 = "Canadian English (Multilingual)"
00000C0C = "Canadian French"
00010C0C = "Canadian French (Multilingual)"
0000041a = "Croatian"
00000405 = "Czech"
00010405 = "Czech (QWERTY)"
00000406 = "Danish"
00000413 = "Dutch"
00000425 = "Estonian"
0000040B = "Finnish"
0000040C = "French"
00000407 = "German"
00010407 = "German (IBM)"
00000408 = "Greek"
00050408 = "Greek Latin"
00010408 = "Greek (220)"
00030408 = "Greek (220) Latin"
00020408 = "Greek (319)"
00040408 = "Greek (319) Latin"
0000040E = "Hungarian"
0001040E = "Hungarian 101-key"
0000040F = "Icelandic"
00001809 = "Irish"
00000410 = "Italian"
00010410 = "Italian (142)"
0000080A = "Latin American"
00000426 = "Latvian"
00010426 = "Latvian (QWERTY)"
00000427 = "Lithuanian"
00000414 = "Norwegian"
00000415 = "Polish (Programmers)"
00010415 = "Polish (214)"
00000816 = "Portuguese"
00000418 = "Romanian"
00000419 = "Russian"
00010419 = "Russian (Typewriter)"
00000C1A = "Serbian Cyrillic"
00010C1A = "Serbian Latin"
0000041B = "Slovak"
0001041B = "Slovak (QWERTY)"
00000424 = "Slovenian"
0000040A = "Spanish"
0001040A = "Spanish variation"
0000041D = "Swedish"
0000100C = "Swiss French"
00000807 = "Swiss German"
0001041F = "Turkish F"
0000041F = "Turkish Q"
00000422 = "Ukrainian"
00000809 = "United Kingdom"
00000409 = "US"
00010409 = "US-Dvorak"
00030409 = "US-Dvorak for left hand"
00040409 = "US-Dvorak for right hand"
00020409 = "US-International"

 

Thursday, 3 January 2008

Unattended.txt (GuiUnttended) TimeZone Index

You can find TimeZone index list below, may be you will need that list while changing unattended.txt.

































































































































































































































































































































































































IndexTime ZoneDescription
000Dateline Standard Time(GMT-12:00) International Date Line West
001Samoa Standard Time(GMT-11:00) Midway Island, Samoa
002Hawaiian Standard Time(GMT-10:00) Hawaii
003Alaskan Standard Time(GMT-09:00) Alaska
004Pacific Standard Time(GMT-08:00) Pacific Time (US and Canada); Tijuana
010Mountain Standard Time(GMT-07:00) Mountain Time (US and Canada)
013Mexico Standard Time 2(GMT-07:00) Chihuahua, La Paz, Mazatlan
015U.S. Mountain Standard Time(GMT-07:00) Arizona
020Central Standard Time(GMT-06:00) Central Time (US and Canada)
025Canada Central Standard Time(GMT-06:00) Saskatchewan
030Mexico Standard Time(GMT-06:00) Guadalajara, Mexico City, Monterrey
033Central America Standard Time(GMT-06:00) Central America
035Eastern Standard Time(GMT-05:00) Eastern Time (US and Canada)
040U.S. Eastern Standard Time(GMT-05:00) Indiana (East)
045S.A. Pacific Standard Time(GMT-05:00) Bogota, Lima, Quito
050Atlantic Standard Time(GMT-04:00) Atlantic Time (Canada)
055S.A. Western Standard Time(GMT-04:00) Caracas, La Paz
056Pacific S.A. Standard Time(GMT-04:00) Santiago
060Newfoundland and Labrador Standard Time(GMT-03:30) Newfoundland and Labrador
065E. South America Standard Time(GMT-03:00) Brasilia
070S.A. Eastern Standard Time(GMT-03:00) Buenos Aires, Georgetown
073Greenland Standard Time(GMT-03:00) Greenland
075Mid-Atlantic Standard Time(GMT-02:00) Mid-Atlantic
080Azores Standard Time(GMT-01:00) Azores
083Cape Verde Standard Time(GMT-01:00) Cape Verde Islands
085GMT Standard Time(GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
090Greenwich Standard Time(GMT) Casablanca, Monrovia
095Central Europe Standard Time(GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague
100Central European Standard Time(GMT+01:00) Sarajevo, Skopje, Warsaw, Zagreb
105Romance Standard Time(GMT+01:00) Brussels, Copenhagen, Madrid, Paris
110W. Europe Standard Time(GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
113W. Central Africa Standard Time(GMT+01:00) West Central Africa
115E. Europe Standard Time(GMT+02:00) Bucharest
120Egypt Standard Time(GMT+02:00) Cairo
125FLE Standard Time(GMT+02:00) Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius
130GTB Standard Time(GMT+02:00) Athens, Istanbul, Minsk
135Israel Standard Time(GMT+02:00) Jerusalem
140South Africa Standard Time(GMT+02:00) Harare, Pretoria
145Russian Standard Time(GMT+03:00) Moscow, St. Petersburg, Volgograd
150Arab Standard Time(GMT+03:00) Kuwait, Riyadh
155E. Africa Standard Time(GMT+03:00) Nairobi
158Arabic Standard Time(GMT+03:00) Baghdad
160Iran Standard Time(GMT+03:30) Tehran
165Arabian Standard Time(GMT+04:00) Abu Dhabi, Muscat
170Caucasus Standard Time(GMT+04:00) Baku, Tbilisi, Yerevan
175Transitional Islamic State of Afghanistan Std.(GMT+04:30) Kabul
180Ekaterinburg Standard Time(GMT+05:00) Ekaterinburg
185West Asia Standard Time(GMT+05:00) Islamabad, Karachi, Tashkent
190India Standard Time(GMT+05:30) Chennai, Kolkata, Mumbai, New Delhi
193Nepal Standard Time(GMT+05:45) Kathmandu
195Central Asia Standard Time(GMT+06:00) Astana, Dhaka
200Sri Lanka Standard Time(GMT+06:00) Sri Jayawardenepura
201N. Central Asia Standard Time(GMT+06:00) Almaty, Novosibirsk
203Myanmar Standard Time(GMT+06:30) Yangon (Rangoon)
205S.E. Asia Standard Time(GMT+07:00) Bangkok, Hanoi, Jakarta
207North Asia Standard Time(GMT+07:00) Krasnoyarsk
210China Standard Time(GMT+08:00) Beijing, Chongqing, Hong Kong SAR, Urumqi
215Singapore Standard Time(GMT+08:00) Kuala Lumpur, Singapore
220Taipei Standard Time(GMT+08:00) Taipei
225W. Australia Standard Time(GMT+08:00) Perth
227North Asia East Standard Time(GMT+08:00) Irkutsk, Ulaan Bataar
230Korea Standard Time(GMT+09:00) Seoul
235Tokyo Standard Time(GMT+09:00) Osaka, Sapporo, Tokyo
240Yakutsk Standard Time(GMT+09:00) Yakutsk
245A.U.S. Central Standard Time(GMT+09:30) Darwin
250Cen. Australia Standard Time(GMT+09:30) Adelaide
255A.U.S. Eastern Standard Time(GMT+10:00) Canberra, Melbourne, Sydney
260E. Australia Standard Time(GMT+10:00) Brisbane
265Tasmania Standard Time(GMT+10:00) Hobart
270Vladivostok Standard Time(GMT+10:00) Vladivostok
275West Pacific Standard Time(GMT+10:00) Guam, Port Moresby
280Central Pacific Standard Time(GMT+11:00) Magadan, Solomon Islands, New Caledonia
285Fiji Islands Standard Time(GMT+12:00) Fiji Islands, Kamchatka, Marshall Islands
290New Zealand Standard Time(GMT+12:00) Auckland, Wellington
300Tonga Standard Time(GMT+13:00) Nuku'alofa