Wrapper Script Perdictement
We've gone from SMS Installer to WiseScript over the past ten years. We have a pretty extensive wrapper template built in WiseScript for bundling vendor installations and deploying via SCCM. Because of the upcoming adoption of Win7 x86 and x64 platforms WiseScript is not as reliable because of its limitations on x64. We've been reluctant to repackage vendor installations. I'm curious if anyone in this community has been through a similar scenario and what they've adopted.
Considerations so far:
WiseScript: Need to dev numerous WiseScript custom actions (UDA) to try and get around the x64 limitations. I have successfully tested a few working UDA examples in regards to the registry but have been unable to use the Execute Program action to launch a 64bit application, such as notepad.exe in 64bit mode.
Windows Installer: Could possibly dev a msi template to deploy vendor installations then have the msi template remove itself after the vendor's install was successfully installed and configured via custom actions. (done it before but not the most elegant)
PowerShell/VBscript: Make a template and use either PowerShell or vbscript directly within the SCCM console to install and configure the applications after successful installation.
AutoIt: Could use AutoIt but without official support this may not be a possibility in our realm.
We try to give the red carpet treatment to our end user's when managing and installing applications on their workstations using simple tools such as WiseScript. With x64 of the horizon it looks like we may need to change our ways. On average we develop at least 5 installation wrappers a day so the ease of the editor with a template is a major plus. If you have been, or are in the midst of, this perdictement your feedback would be appreciated.
Considerations so far:
WiseScript: Need to dev numerous WiseScript custom actions (UDA) to try and get around the x64 limitations. I have successfully tested a few working UDA examples in regards to the registry but have been unable to use the Execute Program action to launch a 64bit application, such as notepad.exe in 64bit mode.
Windows Installer: Could possibly dev a msi template to deploy vendor installations then have the msi template remove itself after the vendor's install was successfully installed and configured via custom actions. (done it before but not the most elegant)
PowerShell/VBscript: Make a template and use either PowerShell or vbscript directly within the SCCM console to install and configure the applications after successful installation.
AutoIt: Could use AutoIt but without official support this may not be a possibility in our realm.
We try to give the red carpet treatment to our end user's when managing and installing applications on their workstations using simple tools such as WiseScript. With x64 of the horizon it looks like we may need to change our ways. On average we develop at least 5 installation wrappers a day so the ease of the editor with a template is a major plus. If you have been, or are in the midst of, this perdictement your feedback would be appreciated.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
aogilmor
13 years ago
forget about all except windows installer. anything customization you need done could be done with CA's, the rest are kludges
Posted by:
anonymous_9363
13 years ago
Agreed but would recommend re-packaging legacy format (i.e. non-MSI) vendor installs into MSI. Wrappers are the lazy way.
Posted by:
hashref
13 years ago
And so the msi templates begin. The wrapper was 'lazy' but it made sense with the workflow. Rather than building a ton of UDAs for WiseScript it does make more sense to write a ton of custom actions for MSIs. Its about time for us to get up to speed, anyway. Thanks for the input.
Posted by:
Nomi1985
13 years ago
You can disable/enable system file/registry redirection on 64-bit system in WiseScripts using the following code. This will allow you to edit the 64-bit registry or access 64-bit versions of programs such as notepad.exe, etc.
The following link is a file I posted on the Symantec Wise forums and contain custom actions which allow you to modify either the 32 or 64-bit registry: http://www.symantec.com/connect/sites/default/files/64-Bit%20Registry%20Custom%20Actions.zip
item: Get System Information
Variable=IS_64_BIT_OS
Flags=00011000
end
item: Remark
Text=If the OS is 64-bit then...
end
item: If/While Statement
Variable=IS_64_BIT_OS
Value=1
end
item: Set Variable
Variable=IS_64_BIT_OS
Value=TRUE
end
item: End Block
end
item: Remark
Text=If the OS is 32-bit then...
end
item: If/While Statement
Variable=IS_64_BIT_OS
Value=0
end
item: Set Variable
Variable=IS_64_BIT_OS
Value=FALSE
end
item: End Block
end
item: Remark
Text=If you need to disable WOW64 file redirection so that you can access 64-Bit OS components and directories on 64-bit systems, use the following code
end
item: If/While Statement
Variable=IS_64_BIT_OS
Value=TRUE
end
item: Remark
Text=Disable WOW64 File Redirection
end
item: Call DLL Function
Pathname=%SYS32%\kernel32.dll
Function Name=Wow64DisableWow64FsRedirection
Argument List=70OLD64FSVALUE
Return Variable=2ERRCODE64FS
Flags=01100000
end
item: End Block
end
item: Remark
Text=Execute/Access 64-bit or 32-bit OS components and directories here.
end
item: Remark
end
item: If/While Statement
Variable=IS_64_BIT_OS
Value=TRUE
end
item: Remark
Text=Enable WOW64 File Redirection
end
item: Call DLL Function
Pathname=%WIN%\SysWow64\kernel32.dll
Function Name=Wow64RevertWow64FsRedirection
Argument List=21%OLD64FSVALUE%
Return Variable=2ERRCODE64FS
Flags=00100000
end
item: End Block
end
The following link is a file I posted on the Symantec Wise forums and contain custom actions which allow you to modify either the 32 or 64-bit registry: http://www.symantec.com/connect/sites/default/files/64-Bit%20Registry%20Custom%20Actions.zip
Posted by:
poojasri
12 years ago
The above script is not redireting... Did any one tried ??? Is there any other script for the same.
Posted by:
victormr
11 years ago
Have you looked into WinBatch + compiler?
It's been around since Windows 3.x and has gown with ever version of Windows.
If your familiar with AutoIt then it's an easy transition.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.