Voice VLAN provision

Back in 2007, I have used Cisco Switch to provision Mitel Voip phone, and phone will use a different VLAN than PC and share the same data drop. However, I forge the technical detail how the hell the Phone is smart enough to get a different VLAN.

Now, I know it is because CDP. Actually, the there are other options, such as DHCP VLAN provision. Polycom SIP phone support CDP as well. Here is the link.

Automatic Configuration of VLAN ID
In the Network Settings menu, there is another field called “CDP”; this controls whether the phone
supports the Cisco Discovery Protocol. Among many other things, CDP allows the Ethernet switch to
inform an IP phone what VLAN ID it should use without requiring manual configuration of each
phone.
4
If CDP is enabled and a VLAN ID is also manually configured, any value received via CDP will
override the manual configuration. If no VLAN ID is received via CDP, the phone will fall back to the
configured value, if present, or to the native VLAN.
QoS Configuration
By default, the phone sends all audio packets with 802.1p tag and IP Precedence values of 5, which
is the highest priority level available for user traffic. This can be adjusted via the
qos.ethernet.rtp.user_priority and qos.ip.rtp.precedence values in the configuration files. Marking
audio packets with DSCP values is currently not supported.

More infomation avaiable at voip-info.org and this link

http://wiki.voiceroute.org/wiki/Overview_of_Auto-provisioning_Phones

ZT: how to add OEM SATA driver

Here is a quick but hopefully useful guide for adding mass storage device drivers to Windows XP SP2 and Windows PE 2005. This guide explains how to add the Intel SATA driver (very common) to scripted install, sysprepped images and Windows PE 2005. Download the IntelSATA drivers (Intel Matrix Storage Manager) from www.intel.com and extract them to a temporary folder, C:\Drivers\IntelSATA in this example The content of the C:\Drivers\IntelSATA folder should have the following files iaahci.cat iaahci.inf iastor.cat iastor.inf iastor.sys txtsetup.oem Adding mass storage drivers to Windows XP unattended setup (scripted, via unattend.txt) On the distribution share, containing the Windows XP SP2 setup files , create a folder structure like \i386\$OEM$\TEXTMODE, copy the C:\Drivers\IntelSATA content to this folder. On the distribution share, containing the Windows XP SP2 setup files , create a folder structure like \i386\$OEM$\$1\Drivers\IntelSATA, copy the C:\Drivers\IntelSATA content to this folder. Modify the unattend.txt file to look like this [MassStorageDrivers] "Intel(R) 82801HR/HH/HO SATA RAID Controller (Desktop ICH8R)" = OEM "Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop ICH8R)" = OEM "Intel(R) 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)" = OEM "Intel(R) 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)" = OEM "Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH)" = OEM "Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)" = OEM "Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)" = OEM "Intel(R) 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)" = OEM "Intel(R) 82801FR SATA RAID Controller (Desktop ICH6R)" = OEM "Intel(R) 82801FR SATA AHCI Controller (Desktop ICH6R)" = OEM "Intel(R) 82801FBM SATA AHCI Controller (Mobile ICH6M)" = OEM "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "Retail" [OEMBootFiles] iaStor.inf iaahci.inf iaStor.cat iaahci.cat iaStor.sys Txtsetup.oem [Unattended] OemPreinstall = Yes OemPnPDriversPath = "Drivers\IntelSATA” DriverSigningPolicy = Ignore Note: the IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "Retail is important for standard IDE failback Adding mass storage drivers to Windows XP for sysprep (imaging) Modify sysprep.inf to look like this . Since we manually update sysprep.inf, do not add BuildMassStorageSection = Yes to the [Sysprep] section [Sysprep] [SysprepMassStorage] ; Added for Intel SATA Controller Support PCI\VEN_8086&DEV_2652&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_2653&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_27C1&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_27C5&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_2681&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_2821&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_2652&CC_0104=C:\Drivers\IntelSATA\iastor.inf PCI\VEN_8086&DEV_27C3&CC_0104=C:\Drivers\IntelSATA\iastor.inf PCI\VEN_8086&DEV_2682&CC_0104=C:\Drivers\IntelSATA\iastor.inf PCI\VEN_8086&DEV_27C6&CC_0104=C:\Drivers\IntelSATA\iastor.inf PCI\VEN_8086&DEV_2822&CC_0104=C:\Drivers\IntelSATA\iastor.inf ; End of drivers added for Intel SATA Controller Support ; ; Generic drivers Adding mass storage drivers to Windows PE 2005 Method 1 (via winpeom.sif), requires one folder per controller and updating of each txtsetup.oem even if the drivers supports many controllers In this example we add support for the PCI\VEN_8086&DEV_2652&CC_0104 and PCI\VEN_8086&DEV_27C3&CC_0104 controllers Note: Both using the same driver Create a folder structure like \i386\system32\Drivers\DiskDrivers\IntelSATA_2652 Create a folder structure like \i386\system32\Drivers\DiskDrivers\IntelSATA_27C3 Copy the content of the c:\tmp\IntelSATA folder to both directories (yes duplicate) In the \i386\system32\Drivers\DiskDrivers\IntelSATA_2652 folder modify the [defaults] section of txtsetup.oem to match the driver In the \i386\system32\Drivers\DiskDrivers\IntelSATA_2652 folder modify the [defaults] section of txtsetup.oem to match the driver Method 2 (via txtsetup.sif), make the driver support all it’s controllers without modifications… Extract the WinPE 2005 iso or compile a custom WinPE 2005 image Copy the iastor.sys file from c:\tmp\IntelSATA to \i386\system32\drivers Modify the \i386\txtsetup.sif folder In the [SCSI.LOAD] section add Iastor = iastor.sys,4 In the [HardwareIdsDatabase] section, add PCI\VEN_8086&DEV_2652&CC_0106 = iastor PCI\VEN_8086&DEV_2653&CC_0106 = iastor PCI\VEN_8086&DEV_27C1&CC_0106 = iastor PCI\VEN_8086&DEV_27C5&CC_0106 = iastor PCI\VEN_8086&DEV_2681&CC_0106 = iastor PCI\VEN_8086&DEV_2821&CC_0106 = iastor PCI\VEN_8086&DEV_2652&CC_0104 = iastor PCI\VEN_8086&DEV_27C3&CC_0104 = iastor PCI\VEN_8086&DEV_2682&CC_0104 = iastor PCI\VEN_8086&DEV_27C6&CC_0104 = iastor PCI\VEN_8086&DEV_2822&CC_0104 = iastor

psexec and pstools

http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

psexec is very useful tool that can be use during deployment
another tool is autorun

Deployment tool - WPKG

My boss like the open source tools and software for many reasons. Here I am evaluating an open source deployment tool, WPKG.

- What it requires?
WPKG require

1. a WPKG network shared folder and a domain account that can access this share folder from everywhere
2. a domain admin account or local-admin-for-all-workstation account to push out the wpkg client service to all workstation, via psexec
3. the network shared folder will has a wpkg.js as the main executable script; and profile.xml and package.xml. The xml files will define the installation details for each software. And host file ( define wich workstation get which profile-package)

- How it works?
http://wpkg.org/Screenshots
http://wpkg.org/WPKG_QUICK_INSTALL
The WPKG Installer will create a windows service on the client machine. The service will run at system boot, and read the configuration xml files from the WPKG network share. The service will be created to run as the local SYSTEM user (the other user credentials discussed below are different).
- How it compare with others?
This is a "pull" type of deployment. It means that workstation initial the installation, by start the service or restart the computer. I don't believe this product can push the deployment although it claim to be a push/pull tool.

one community advantage is it has a collection of silent installer detail, including software A-Z and windows hotfix.
http://wpkg.org/Category:Silent_Installers

- Conclusion
compare with other tools, Altiris , SMS, which can push out a software installation. This product is not strong.

It seems don't provide any other functions other than install software. It has no database, no inventory of computer specs. It need you to familar with the technical detail of unattended mode of the each application. It won't do the after-install configuration. So the use is quite limited.

- Testimonial
I read through, and found that many has mentioned the it can install other non-msi software.
http://wpkg.org/Testimonials

Acronis Universal Restore summary and errors

Acronis UR will work 60% at the first attempt when restore to a dissimillar hardware by specify a Chipset driver or storage driver. And for some type of machine, the restore always works fine.
For example, the DELL 630. I have restored a VM image , a HP compaq d530 image, a DELL 170 image. And every single time, the Acronis UR replace the driver correctly and the DELL 630 laptop just boot up fine. After log in, I need to go through those non-boot-essential PnP drivers, and install them so that I can clear those question mark in the device manager. I still need to run the chipset driver setup again, because it has a set of devices depend on.

The other 40% time I have failed at the first attempt, but I get it boot up eventually. These model are DELL optiplex 330, and DELL D620.

Two type of errors have occure to me.
First, it is that restore progress bar is not moving any more when it has only 7-12 second left. I force power off the machine and power on to interrupt and it actually boot up fine. So this error can be ignore
Second, the restore operation is successfully as the pop up says, but windows XP will reboot itself after seeing XP splash logo briefly. I found the Acronis log has a warning about can not locate a file. The correct steps right now is:
1. Make a disk to disk restore, which will delete the target disk; partition to partition won't delete disk or MBR.
2. see if there are error in log, if yes, launch the recovery again without test the booting
3. maek a partition to partition restore without select MBR; resize the partition necessary to take all space on target
4. specify the drivers
5. if this is not working, then do not specify the driver from USB key, but specify check box on "search removable medium" in next page; In this way, I let Acronis to search driver instead of providing driver from my USB key
6. If the log has not entry, it is working. Give it a power boot.

regenerate a GUID for TM client

TM installation come with a imgsetup.exe file that enable you to seal the image and let it run at next reboot and generate an unique GUID while report to TM server.

See this link for detail.
http://blog.itprohelp.com/2009/04/imaging-pcs-with-trend-micro-officescan.html

command line switch - update.exe and hotfix.exe

Overview of the installation process

When you run a Windows software update package without command-line switches, the Hotfix.exe or Update.exe Setup program is automatically run to install the software update. The following actions are performed by the Setup program:

• The installation program (Hotfix.exe or Update.exe) examines the service pack version you currently are using. If your service pack version is earlier than the software update version, but not earlier than the minimum version specified by the software update, and the language is the same, the Setup program automatically installs the software update. If your service pack version is later than the software update version, the installation does not continue.
• If the software update language version does not match your operating system language, the installation does not continue.
• If no version conflict exists, Hotfix.exe or Update.exe installs the software update.
• The installation program registers the software update under one of the following registry keys:
  HKEY_LOCAL_MACHINE \Software\Microsoft\Updates\\\KB
  HKEY_LOCAL_MACHINE \Software\Microsoft\Windows NT\CurrentVersion\Hotfix\Q
  HKEY_LOCAL_MACHINE \Software\Microsoft\Windows NT\CurrentVersion\Hotfix\KB
• Removal information for the software update is stored in a hidden folder named $NtUninstallQnnnnnn$ or $NtUninstallKBnnnnnn$ in %Systemroot%.

Back to the top

Command-line switches for the Update.exe program

The following tables list the command-line switches that are supported by each different version of the Update.exe program.

Collapse this tableExpand this table

Standard switch	Description of the switch	Versions of Update.exe that support this switch
/help	Displays command-line help.	Version 5.3.24.3 and later versions support the /help switch. For compatibility with older versions, the /? switch can be used.
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.	Version 5.3.24.3 and later versions support the /passive switch. For compatibility with older versions, the /u switch can be used.
/quiet	Quiet mode - same as unattended mode, but no status or error messages are displayed.	Version 5.3.24.3 and later versions support the /quiet switch. For compatibility with older versions, the /q switch can be used.
/norestart	Do not restart the computer when the installation is finished.	Version 5.3.24.3 and later versions support the /norestart switch. For compatibility with older versions, the /z switch can be used.
/warnrestart	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (Default is 30 sec). Intended for use with either /quiet or /passive switches.	Version 6.1.22.0 and later versions support the /warnrestart switch.
/forcerestart	Restart the computer after installation and force other applications to close at shutdown without saving open files first.	Version 5.3.24.3 and later versions support the /forcerestart switch.
/promptrestart	Presents a dialog box to prompt user to restart if required. Intended for use with /quiet.	Version 6.1.22.0 and later versions support the /promptrestart switch.
/forceappsclose	Forces other programs to close when the computer shuts down.	Version 5.4.15.0 and later versions support the /forceappsclose switch. For compatibility with older versions, the /f switch can be used.
/nobackup	Do not back up files for uninstall.	Version 6.1.22.0 and later versions support the /nobackup switch. For compatibility with older versions, the /n switch can be used.
/overwriteoem	Overwrite OEM files without prompting.	Version 6.1.22.0 and later versions support the /overwriteoem switch. For compatibility with older versions, the /o switch can be used.
/integrate:path	Integrates the software updates into the Windows installation source files located at the path specified. Note that :path refers to the folder that contains the i386 folder.	Version 5.4.15.0 and later versions support the /integrate:path switch. For compatibility with older versions, the /s switch can be used.
/log:path	Allows user to specify where to create the log file.	Version 6.1.22.0 and later versions support the /log switch.
/ER	Enable extended error reporting.	All versions support the ER switch.
/verbose	Enable verbose logging. Creates %Windir%\CabBuild.log upon install that details files to be copied. Using this switch may cause the installation to occur much slower.	Version 5.3.24.3 and later versions support the /verbose switch. For compatibility with older versions, the /v switch can be used.
/d:path	Specifies a backup directory for Windows Service Pack installation. :path indicates the destination folder for the backup files. The default backup location is %Systemdrive%\$ntservicepackuninstall$.	This switch is not available for updates other than Service Packs and is available only in Installer versions 5.3.16.5 and later versions.
/extract[:path]	Extracts files without starting Setup. If ":path" is not included, you are prompted for the path of a destination folder to extract the files. If ":path" is used, the files are extracted to the specified destination folder.	Version 5.3.24.3 and later versions support the /extract switch. For compatibility with older versions, the /x switch can be used.
/hotpatch:disable	Disables hotpatching functionality, and installs the cold patch only.	This is only to be used for Windows Server 2003 packages that support hotpatching and is available in versions 6.1.22.0 and later. For more information on hotpatching, see the "References" section in this article for a link to the "Inside Update.exe" whitepaper.

Notes

• We are adopting a consistent set of command-line switches that you can use to deploy packages that contain software updates. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  824687 (http://support.microsoft.com/kb/824687/ ) Command-line switches for Microsoft software update packages
  For backward compatibility, Windows software updates that implement the new standard switch names also support the setup switches that are used by the earlier version of the Update.exe. However, we recommend that you stop using the old switches because this support may be removed in future software updates.
• All the switch options that are listed use a forward slash (/). For compatibility with older versions, a hyphen (-) can still be used instead of the forward slash (/).
• To safely remove a software update, remove the one most recently installed first. For example, assume that hotfix A and hotfix B both replace the same file or registry keys, and that you installed hotfix A before you installed hotfix B. To return your system to the state before the installation of hotfix A, you must uninstall hotfix B before you uninstall hotfix A. For more information about how to remove Update.exe updates, click the following article number to view the article in the Microsoft Knowledge Base:
  823836 (http://support.microsoft.com/kb/823836/ ) Removing Windows software updates in the wrong order may cause the operating system to stop functioning

AppDeploySM Package Knowledge Base

Class Act Variants 0.x

Company: University of Aberdeen
Setup type: Native Windows Installer setup (MSI)
Package Difficulty Rating: not yet established
Most Commonly Reported Method Used: not yet established

---

Notes

---

These are a series of Educational programs written by University of Aberdeen.

Although the applications are standard MSIs, when you first run them you are prompted for a serial code, and then prompted to accept the EULA.

Each of these steps creates a file in the same folder as the executable.

Here's the steps I used..

Install the MSI on a test PC, run it, enter the serial, and accept the EULA.

Browse to the folder of the exe - usually C:\Program Files\Educational Networking\[something]

Copy the files license.lic and tocagreed.yes to a server folder.

Now on your deployment script, it should be a simple case of run the MSI, and then copy these two files back.

In my case, the school purchased about 15 sub-packages, each with their own MSI.. I used a small autoit script which does them en-masse..

Each of these also needs .NET 3.5 (version 3521022), so I have the script check for it and install it if it isn't there.


Apologies in advance for the shocking code - you're more than welcome to tidy it up! :-)

Folder structure is:
[autoit script compiled exe]
Folder called LicFiles containing the 2 files listed above
Then as many sub-folders as needed containing the MSIs for each sub-program.
Folder called DotNet35
within that:
silent.bat
dotnetfx35.exe
hotfixes\NDP20SP2-KB958481-x86.exe
hotfixes\NDP30SP2-KB958483-x86.exe
hotfixes\NDP35SP1-KB958484-x86.exe
hotfixes\WindowsXP-KB961118-x86-ENU.exe

DotNet35\silent.bat is:
start /wait dotnetfx35.exe /q:a /c:"setup.exe /q /norestart" /norestart
start /wait hotfixes\NDP20SP2-KB958481-x86.exe /passive /norestart
start /wait hotfixes\NDP30SP2-KB958483-x86.exe /passive /norestart
start /wait hotfixes\NDP35SP1-KB958484-x86.exe /passive /norestart
start /wait hotfixes\WindowsXP-KB961118-x86-ENU.exe /quiet /norestart

Autoit script code:
; Install Class Act Variants

#Include <_filelisttoarraynew2g.au3>
#Include

; Search through for all MSIs in the folder, and install 'em

Dim $Syntax
Dim $Header
Dim $MSIFilesArray[100]
Dim $FilesArray[100]
Dim $BatFile

$BatFile = @TempDir & "\CA.bat"

$Syntax = "@Echo Off" & @CRLF
$Header = ""

Dotnetcheck()
ListMSIFiles()
InstallApps()
RegisterApps()

EXIT


; ===================================================================================
Func dotnetcheck()

$DotNetVerNum = 0
$DotNetVerMin = 3521022

; Check if .NET 3.5 is installed

$DotNetKey = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5"
$DotNetVer = RegRead($DotNetKey, "Version")

If @Error = 0 then
$DotNetVerString = StringReplace($DotNetVer, ".", "")
$DotNetVerString = StringMid($DotNetVerString, 1, StringLen($DotNetVerMin))
$DotNetVerNum = Number($DotNetVerString)

;msgbox(0, "", $DotNetVerString & @CRLF & $DotNetVerNum)
EndIf


If $DotNetVerNum > $DotNetVerMin then
Return
EndIf

; Generate .NET 3.5 installer

$DotNetDir = @ScriptDir & "\DotNet35"
$DotNetBATFilename = "silent.bat"

If FileExists($DotNetDir & "\" & $DotNetBATFilename) then
$Syntax = $Syntax & "PUSHD " & Chr(34) & $DotNetDir & Chr(34) & @CRLF
$Syntax = $Syntax & "CALL " & Chr(34) & $DotNetBATFilename & Chr(34) & @CRLF
$Syntax = $Syntax & "POPD " & @CRLF

EndIf

EndIf
EndFunc
; ===================================================================================


; ===================================================================================
Func ListMSIFiles()
$Filter = "*.msi"
$iFlag = "1" ;files only
$i_recurse = "1"

$MSIFilesArray=_FileListToArray3(@ScriptDir, $Filter, 1, 1)
If @Error = 0 then
If $MSIFilesArray[0] > 1 then
For $loop = 1 to $MSIFilesArray[0]
$Syntax = $Syntax & "MSIEXEC /i " & Chr(34) & $MSIFilesArray[$loop] & Chr(34) & " /qn /norestart" & @CRLF
Next
EndIf
EndIf
EndFunc
; ===================================================================================


; ===================================================================================
Func InstallApps()

$Log = FileOpen($BatFile, 2)
FileWriteLine($Log, $Syntax)
FileClose($Log)
RunWait($BatFile, @ScriptDir, @SW_HIDE)
EndFunc
; ===================================================================================


; ===================================================================================
Func RegisterApps()
; Copy the licence and EULA acceptance files to each folder

$Dir = @ProgramFilesDir & "\Educational Networking"
$Filter = "*.exe"
$iFlag = "1" ;files only
$i_recurse = "1"
$LicDir = @ScriptDir & "\Licfiles"

$FilesArray=_FileListToArray3($Dir, $Filter, 1, 1)
If @Error = 0 then
If $FilesArray[0] > 1 then

For $loop = 1 to $FilesArray[0]
$exe = $FilesArray[$loop]
$break = StringInStr($exe, "\", 0, -1)
If $break <> 0 then
$exedir = StringMid($exe, 1, $break -1)
;msgbox(0, "", $
FileCopy($LicDir & "\*.*", $exedir, 1)
;msgbox(0, "", $exedir)
EndIf
Next
EndIf
EndIf
EndFunc (Provided by sirclive)

---

Command Lines

---

No Entries.

---

Related Links

---

No Entries.

---

Lockdown Information

---

No Entries.

---

http://www.appdeploy.com/packages/detail.asp?id=1508

Exisint image file - Universal restore

http://www.acronis.com/r/support/en/kb/502/aur_restore.html