Wise Package Studio 6.0 - News


Calendars

Community Center (formerly old YMCA) Thursdays from 5:30-6:30 pm each week. $10 per student each week and 1/2 price for an immediate relative of a student. Class textbook and CD package will be available for $15. (276) 679-2096 or (276) 679-0754.



Calendars

Family package $15. (423) 913-3246 or www.historicjonesboroughdancesociety.org. LAY'S HARDWARE CENTER FOR THE ARTS: Coeburn, Va., 409 Front St., May 27, 7:30 pm Runaway Freight. Doors open 6 pm $5 adults/$1 children 6-12. (276) 395-5360, (276) 395-3323



Digital Domain builds presence in Florida

"With that housing, it began to feel like a large city, population-wise, but was functioning as a bedroom community, where people were going elsewhere for many jobs, except for the construction industry," Mowry said.




64-bit Windows registry and WiseScript Package Editor


Can someone explain this to me? I'm seeing different behavior on two similar PCs depending on whether I run a VBScript or run that same script within a Wise-created EXE.

My PC is Windows XP Professional x64 Edition, Version 2003, Service Pack 2.
I'm trying to read the "Install" value (a dword value) for registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1. This key exists both on my PC and a test PC, which is also XP Pro 64 bit, etc.

This is the VBScript I'm using:
Const HKEY_CURRENT_USER = &H80000001 Const HKEY_LOCAL_MACHINE = &H80000002 strComputer = "." Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_ strComputer & "\root\default:StdRegProv") strKeyPath = "SOFTWARE\Microsoft\PowerShell\1" strValueName = "Install" oReg.GetDWORDValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,dwValue MsgBox "Install value is: " & dwValue

Don't have error handling built in yet because I'm still testing.

This script reports back the value of "Install" correctly both on my PC and the test PC. So far so good.

Next I wrote a Wise package (using Wise Package Studio 8) with the WiseScript Package Editor. It copies the VBScript locally and then runs it. Here's the Wise code:
item: Set Variable Variable=C Value=C: end item: Install File Source=.\MSI\script\dword.vbs Destination=%C%\test\dword.vbs Flags=0000000010100010 end item: Execute Program Pathname=%C%\test\dword.vbs Flags=00000010 end

I compile in Wise to an EXE and then run it. On my PC the message box shows me the correct value for "Install", which is "1." But on my test PC, it doesn't report back any value at all. So I'm not sure why the VBScript behaves correctly on both PCs, but calling the VBScript via a Wise-created EXE results in my PC reporting correctly and the other not. I've tested against a third 64 bit XP machine, also, just to make sure my results weren't a fluke.

What I'm trying to do specifically is check if PowerShell is installed on a PC. I realize that for this particular example I can also check if the directory exists in Wise, but for my particular task at hand, there will be instances when I have to check the registry, and right now I know of no reliable way to do it when my target PC is 64 bit.


Wise Package Studio 6.0 - Bookshelf

The Definitive Guide to Windows Installer Technology for System Administrators

The Definitive Guide to Windows Installer Technology for System Administrators

Wise Package Studio The Wise Package Studio is a popular tool for system administrators who want to repackage installations into MSI tools. ...

SMS 2003 Recipes: A Problem-Solution Approach

SMS 2003 Recipes: A Problem-Solution Approach

Visit the Wise Package Studio web site for detailed information on the latest ... The Standard Edition is similar in features to the Wise Package Studio ...

Administrator's Guide to Active Directory

Administrator's Guide to Active Directory

... purchase a package such as Wise's Wise Package Studio (http://www.wise.com/ wps.asp). Wise Package Studio will read your Visual Studio or Visual Studio . ...

Microsoft Windows Vista Administration

Microsoft Windows Vista Administration

Altiris Wise Package Studio If your organization has a license for the Wise Package Studio, you may have a cost-effective solution for capturing application ...

Deploying Visual FoxPro Solutions

Deploying Visual FoxPro Solutions

Appendix B How To: Wise for Windows Installer Wise for Windows Installer is a ... Inc. Wise also markets other setup tools including Wise Package Studio, ...

Information Today Directory


CONNECTOR 6.0 FOR WISE PACKAGE STUDIO HELP
The Wise Connector lets you edit and validate any .MSI package on the ... Altiris Console using Wise Package Studio tools. It also lets you import .MSI packages ...

Release Notes for Wise Package Studio 6.01
Wise Package Studio helps system administrators and desktop integration teams streamline ... If any existing, pre-6.0 Wise Package Studio databases contain custom tables ...

Wise Package Studio Getting Started Guide
Wise Package Studio. The software described in this book is furnished under a license ... Versions of Wise Package Studio earlier than 6.0 did not enforce this. ...

Harish Yedlapalli | LinkedIn
Experience with Wise Package Studio Professional 3.2/7.0 to automate the installations ... Windows XP, Wise Package Studio 6.0, Microsoft Installer, VB Script, Wise script, MS ...

Altiris delivers unique patch risk and impact assessment...
...with latest release of Wise Package Studio New Wise Package Studio helps minimise patch management hazards and focuses testing efforts to achieve error-free patch ...
TOP