2way Technology

Configuration Manager, Windows 7 OSD, Scripting, Application Packaging, Windows Embedded, Microsoft Surface

Recent posts








    The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

    Hyper-V No active network adapters found

    Recently I installed Hyper-V R2 onto a Lenovo T510 Laptop to be used as a Wise Package Studio Application Packaging Server.

    This is somewhat of an inexpensive server to support two packagers working on site for a Government client for a short period of time. The short story is, they want all of the packaging to be performed on site but they don't have any packaging infrastructure.

    Option "A" is to take a DL360 G4 server onsite and work off that but the simple fact is the two quad-core CPUs and 15K SCSI disks are a bit too heavy and noisy to work with. It's also a bit much to ask my staff to carry a 1U server with them to a client site along with everything else they need to take.

    So the answer is we have a Lenovo T510 Laptop running the Core i7 Quad-Core with 8GB of RAM. It has Hyper-V 2008 R2 installed straight onto the disk (not Server 2008 R2 with the Hyper-V Role) and from there it has a Windows Server Guest running DHCP (for the packaging clients) as well as SQL and Wise Package Studio. There is enough resources left to run a Guest Windows 7 client or two for packaging and testing if needed but the idea with this is to use the Lenovo Laptop as a mobile Wise Package Studio server setup which our Packaging staff can easily take with them for on-site packaging engagements.

    In order to get Hyper-V working on the T510 there was a couple of steps I had to do:

    1. Enable Virtualisation in the BIOS

    2. Install the Network Drivers into Hyper-V.

    On the T510 Laptop, the drivers for the NIC are not available in the Hyper-V R2 install WIM and the Windows 7 x64 drivers from Lenovo don't work with Hyper-V. In the end, the solution was to download the NIC drivers from Intel from here: http://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/18725/eng/PROWinx64.exe&agr=&ProductID=&DwnldId=18725&strOSs=&OSFullName=&lang=eng. I then had to use the Hyper-V pnputil command:

    pnputil -i -a e1k62x64.inf

    Once this command was run the Intel 82577LM Gigabit Network Adapter was installed. From here was a simple case of installing a Guest Virtual Machine using the Microsoft Hyper-V Manager as part of the Remote Administration Tools for Windows 7.

    At this stage the mobile packaging server is working well.



    Posted: Mar 09 2011, 21:39 by Ben Fisher | Comments (0) RSS comment feed |
    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5

    OSD Task Sequence - Set Computer Name to Serial Number

    SCCM OSD Task Sequence - Set Computer Name based on Serial Number

    When performing 'bare-metal' builds with MDT or Configuration Manager Operating quite often in a Task Sequences you need to set the target systems computer name prior to joining the domain. The WinPE default MININT-XYZXYZ - whilst it is automatically generated will help ensure a target system completes the build without user intervention (e.g. Zero Touch) it doesn't really cut it. To keep with the zero-touch capability, one option is to use the serial number which can be easily extracted from the BIOS using a WMI query.

    One of the great things about using the serial number is it doesn't rely on the presetting of something like the Asset Tag - whilst this is a very popular method of setting computer names, I personally don't like Asset Tags because when I find myself as a consultant in a larger environments (e.g. 30,000+ PCs) and I see plenty of Asset Tags values not preset. In these cases, a build will either fail (depending on your build error handling logic) or it will receive the MININT-XYZXYZ name. Long story short, using the Serial Number is what I like to call an 'assured outcome' because the serial number will always be preset, it's not reliant on a 'person' setting it when a company receives the computer and sticks an asset tag on the exterior of the computer.

    There are a number of sample scripts out there which will help you set the computer name using the Serial Number extracted from WMI, this is fairly easy and straight forward. But.. there are some scenarios which are not catered for in most of the examples floating around on the Internet. For example:

    • Computer names can't exceed 15 characters
    • Computer names can't start with a numerical character (e.g. 0-9)
    • Computer names can't contain spaces

    The following script will set the computer name whilst taking into consideration the above scenarios:

    On Error Resume Next

    Dim objWMIService
    Dim colItems
    Dim colBattery
    Dim objSMSEnv
    Dim strNewName

    Set objWMIService = GetObject("winmgmts:\\.\root\CIMV2")
    Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_Bios")
    Set colBattery = objWMIService.ExecQuery("SELECT * FROM Win32_Battery")

    ' Get the Serial Number
    For Each objItem In colItems
        ' Remove all beginning, trailing and containing spaces and change to all upper case
        strNewName = UCase(Trim(Replace(objItem.SerialNumber, " ", "")))

    ' Is this a Desktop or a Laptop
    If colBattery.Count = 1 Then
        ' Is a Laptop
        strNewName = "L" & strNewName
        ' Is a Desktop
        strNewName = "W" & strNewName
    End If

    ' If the name is longer than 15 characters, we need to truncate it
    If Len(strNewName) > 15 Then
        ' If the name contains "-" characters (e.g. VM's), remove them
        If InStr(strNewName, "-") > 0 Then
            strNewName = Replace(strNewName, "-", "")
        End If
        ' If the name is still longer than 15 characters, truncate it to first 15
        strNewName = Mid(strNewName, 1, 15)
    End If

    ' Set the Environment Variable that controls the Computer Name
    Set objSMSEnv = CreateObject("Microsoft.SMS.TSEnvironment")
    objSMSEnv("OSDCOMPUTERNAME") = strNewName

    Set objSMSEnv = Nothing
    Set colItems = Nothing
    Set colBattery = Nothing
    Set objWMIService = Nothing


    If you're encountering issues with retrieving information from Win32_Battery from within WinPE, add a Task Sequence - Run Command Line item just before you call the Set Computer Name script, use the following Command Line:

    • drvload X:\Windows\inf\Battery.inf


    Feel free to use this script in your Task Sequences.

    Posted: Jan 21 2011, 23:43 by Ben Fisher | Comments (3) RSS comment feed |
    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5
    Filed under: OSD | SCCM 2007 | SCCM 2012

    Software Installation Using Group Policy Startup Scripts

    Recently I was engaged by a large Government client to investigate some issues with what they thought was some poorly packaged applications. The client had previously engaged an small external consultant operating under their own company and unfortunately they didn't really get what they thought they were paying for. During the time spent at this client site I identified a number of issues which I seem to come across quite often so I decided I'd write a blog entry on it.

    The background to this is the client had the SAPGUI application packaged by an external consultant. Anyone who knows SAPGUI knows for various reasons it can be a bit of a challenge to package. The vendor supplied installer for SAP not only installs differently to most other vendor supplied installers but it also does some funky things in areas such as add a heap of entries to the Services file found in %windir%\System32\drivers\etc\Services.

    It also has a number of pre-requisit software products - such as the .Net Framework and two versions of the Visual C# Runtimes (2005SP1 and 2008SP1). These pre-requisits aren't so much the problem unless they're accidently captured and included within the main SAP package (which the previous consultant did) at which point I consider it to be a 'dirty package'.

    In this case, the situation is the client deploys their software (for the moment) using Group Policy Software Installation and the main symptom the client was reporting was the SAP application was initiating self-healing as well as reinstallation each time the computers started up. Initially I thought to look at areas such as Advertising information and user-based Components being located in machine level installed Features as well as the usual run-of-the-mill dirty and orphaned components which should have been removed. Initially I concluded a number of areas within the consultants MSI could be the cause of the problems as these are typically the most common causes for applications repackaged into MSI installers to produce these sorts of problems. I also made an assumption the consultant who did the packaging to have included the Services file in their package which is a big mistake. Unfortunately this assumption also turned out to be true.

    When I opened up the package in Wise Package Studio I discovered all of the above. Multiple features, dirty orphaned components which should have been cleaned out, pre-requisit components included in the main package (such as the Visual C# Runtimes, Visual Basic redistributables and .Net Framework components) as well as the Services file stored in the package as a file and not set as Permanent which means when the package is uninstalled it will remove the Services file completely along with the standard Windows entries. All of these mistakes could result in breakage of the clients SOE when the application is upgraded - which was one of my primary tasks for this engagement.

    The first thing I set out to do was repackage the latest version of SAP GUI correctly and cleanly. Doing so reduced the size of the compiled MSI from 180MB for SAP GUI 7.1 down to 90MB for 7.2. By ensuring the pre-requisit components - .Net Framework 3.5, Visual C# Runtimes 2005 SP1 and Visual C# Runtimes 2008 SP1 are handled separately as well as utilising Merge Modules for XML as well as a range of Visual Basic redistributables meant my SAP GUI package was shaping up just nicely.

    When I started looking at the existing Group Policy object which controls the Software Installation I discovered something very interesting - that being the Policy not only installs the software using the expected Software Installation type but there was also a Machine Startup Script defined. I thought, what's this? Better take a look. What I found was the previous consultant not only setup the MSI they packaged to deploy as a Software Installation Policy but they also created a Machine Start-up Batch File to do the same. Only the consultant didn't think it through clearly because they failed to correctly handle the fact that the Script should only execute the installation if the software isn't already installed. Instead, the way the consultant set it up was each time the script ran it called the installation ragardless if the software was already installed - in other words, each time the target computers started up the script would run and the SAP GUI application installer would be re-executed and the SAP GUI MSI would be reinstalled over the top of the existing installation.

    Once the new version of the SAP GUI application had been re-packaged cleanly the next thing was to discuss with the client how they wanted to address the issues which would arise from uninstalling the previous packaged version of SAP GUI and ensure they knew the risks. At time of writing this blog entry the client is still considering all of the options I've suggested but what I can say is they're currently more inclined to re-image all of the PCs with the old package installed. This approach to me is major work and is avoidable, but the biggest thing it demonstrates is the dangers of inexperienced Application Packagers working in large environments. Unfortunatley it's not an isolated case and I have seen entire SOE fleets being reimaged due to poorly packaged applications.

    I guess the point of this Blog entry is to highlight the importance of building in logic within your Startup scritps if you're using them to install software to ensure they only run when needed. Make sure you Startup script checks to see if the application is already installed or not and only run the installation if needed. Startup scripts running things like Software Installations are becoming more common, for example Office 2007 installed by a Startup script instead of the native Software Installation policy produces far better results and Microsoft is even now providing a downloadable sample script.

    Posted: Aug 25 2010, 11:16 by Ben Fisher | Comments (0) RSS comment feed |
    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5

    BPOS - Exchange Online Performance

    Well it's been a little over a month since migrating to Exchange Online supplied through the BPOS service offering.

    So far the service has been overall really good but I though it's important to share a few 'limitations' and perhaps bugs.

    Additional Mailboxes

    The first issue which has come to our attention is the support for Additional mailboxes. Whilst you can add supplemental mailboxes to Outlook there are a few steps you have to do in order to setup the security permissions. To enable your primary mailbox to have access to additional mailboxes you have to execute a PowerShell command which grants Full Control and SendAs rights. This is no so bad as the PowerShell script works and all you have to do is use your variables. Microsoft has the syntax documented here: http://www.microsoft.com/online/help/en-us/helphowto/f83a224b-53c5-48b4-8e72-327571c4555e.htm

    Add-MSOnlineMailPermission -Identity user@example.com -Credential $cred -TrustedUser admin@example.com –GrantFullAccess True –GrantSendAs True

    The next thing you do is add the account to your Outlook as a secondary mailbox, this you do as you would normally.

    Where the 'bug' appears is Outlook struggles to open emails which are bigger than a typical size email in particular emails which contain attachments over say 500KB. If you try to open an email with say a 3MB attachment you might as well go away and make yourself some lunch because Outlook takes a long time to open the email. If you try to save the attachment locally you also notice the same performance issues. I've noticed these issues don't exist if the email is in the primary mailbox.

    Posted: Aug 05 2010, 15:51 by Ben Fisher | Comments (0) RSS comment feed |
    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5

    Now Using Microsoft BPOS & Exchange Online!

    We've taken a huge plunge, we've migrated one of our primary business domains to the Microsoft Hosted Business Productivity Online Suite (BPOS).

    Initially BPOS purely represented as a stop-gap measure to buy some time whilst we prepared our own in-house Exchange Server infrastructure, now it's looking at becoming a permanent solution for our business. BPOS was chosen because it offered a relatively quick and painless method to move one of our growing businesses from a standard web host type offering that consisted of SendMail/Horde to our own business grade Exchange Server system which we were in the process of building, problem being is we were in desperate need of it sooner than we could deliver it. We already run our own Exchange infrastructure for a number of other domains but the server is well and truely over capacity and we didn't want to push the existing Exchange Server any further.

    Microsoft's on-line service offering presented our company with an immediate solution and the process also presented our business with a number of opportunities to learn and experience first-hand what an every day customer would have to go through if ever they chose to go down this same path.

    First, by moving one of our business domains over to the hosted solution we could experience first-hand what it was like to migrate between systems. I'm not talking about the technical aspect because on that front we have full confidence in our team of engineers, but more the business emotions such as the concerns and stresses that go with moving a mission critical system from one platform to another. Secondly we could experience the service and support offered by Microsoft's Online services first-hand. These two learning experiences would become invaluable knowledge for when discussing products like Microsoft BPOS and Exchange Online to clients and prospects.

    I also think as a solutions provider it's important to endorse the products and services you recommend to clients and how much of a stronger endorsement can you give than buy using them within your own organisation.

    First Steps

    For us the first step was to expand our existing Telstra Dealership to include the T-Suite range of products. The driver behind this is because Telstra's T-Suite is the only way in which Australian customers can obtain access to Microsoft's On-line services. Given our company has already recognised the "cloud" is the way of the future, we thought it was a good opportunity to get onboard and establish as a Microsoft Online Services Advisor as well as Telstra T-Suite Partner and start discovering what opportunities this clould offering presented and how well it performs.

    To achieve this we had to enroll as a Microsoft On-line Services Advisor and have this reflected within our Microsoft Partner profile, this was achieved by completing a number of Microsoft Partner Learning Tutorials and subsequently passing a number of Microsoft on-line exams, overall not difficult but did take some time. Once Microsoft processed our application and exams we were able to apply for the T-Suite Partner Programme, again nothing difficult but took some time for it to be processed. Although there appeared to be some technical issues between Telstra and Microsoft I have to say Telstra was exceptional, in particular Dave Carden not only got our application processed but he also responded to a number of enquiries out of hours and on weekends. From where I stand this is a real change in attitude from Telstra towards customers, it's as though they're realising customer experience and satisfaction pays dividends. Thanks Dave for your efforts, it was well recognised.


    The migration to Exchange Online for us was simple. All we had to do was get the BPOS suite setup along with adding the domain and creating the required user/email accounts, this was very straight forward and it's all performed within a single Administration Console. Having technical expertise in the back end products that deliver the On-line services offering (Active Directory, Exchange, DNS etc) certainly helped with this. When Exchange was setup and the user accounts were created all that was left was to migrate the email from the old system into Exchange, this was done through a series of steps to export from Horde and once Outlook was configured to connect to the hosted Exchange server, we just imported the mail via Outlook.

    When we were confident everything was right to go we updated the MX record on the domain to point to the new servers and within an hour mail was flowing in and out of Exchange On-line. I then went to reconnect my Blackberry, this is the only area where some problems have been encountered. Because the emails were migrated from the old system to the new system, this has created a situation whereby Blackberry considers the emails to be new and now my Blackberry is being bombarded with some 1000+ emails - bit of a pain really especially considering they're not arriving in the correct date order. I personally think Blackberry's sychronisation through Outlook Web Access is less than satisfactory.


    So far we've only had to submit two support tickets to Microsoft. One was because during our testing on older Windows XP systems running older versions of Office you're required to install an Outlook 2003 Connector in addition to the Sign-on software. For some reason the Outlook 2003 Connector wasn't configuring the Exchange Server connection correctly and on these computers we couldn't get Outlook 2003 working with Exchange On-line. Suprisingly this ticket was responded to and subsequently resolved overnight which was satisfactory for this type of low severity ticket.

    The other support ticket related to an enquiry about using Exchange On-line in a slightly different method whereby Exchange On-line is only used for some email accounts for a given domain and other email accounts reside on a separate email server - such as one hosted elsewhere or in-house. Whilst this ticket was also responded to overnight the respondent completely misunderstood the nature of the enquiry and provided a response that was of no assistance. We replied to the ticket but 3 days later we are yet to receive a response.

    Overall the support response received could have been better. Sure our support tickets were set low priority (as specified in the ticket by us) but in the web hosting industry, even low priority tickets generally get responded to within a couple of hours. I would like to think if we ever encountered a major issue such as an outage resulting in business impact a more timely response will be received. It does play on my mind that we don't have a direct line of communication (i.e. phone) to reach Technical Support personnel, even if they just published a phone number that diverts to Microsoft's off-shore support centers it would provide huge peace of mind because if the whole system goes offline for whatever reason, how are we supposed to submit a ticket, let alone get any communication from them about ETAs for service restoration?

    What To Consider

    The key issue I would stress to anyone looking at this type of solution is the support. Make sure you're comfortable knowing there isn't someone you can just call on a whim and say 'make it work' like you can when you're running your own IT infrastructure and have an IT Managed Services provider looking after it. It does concern me we have now handed the control of our entire email system, support, security, backup and maintenance over to another company who won't neccessarily always act in our best interests let alone have anywhere near the level of urgency and due care towards our business. We know how meticulous we are with our systems and our client systems and we know what it takes when responding to a client reporting something like a critical email server is down because we are emotionally connected to the situation (be it ours or a clients), but you can't expect the same from a company who provides services to such a massive scale of customers, there will never be an emotional connection, therefore there will never be a committment driven by the dedication to achieve the same outcomes as those driven by emotional dedication. The only way you'll get that type of committment from large service providers is if you're a large company with a budget of equal proportion but in this case you wouldn't be looking at services like BPOS anyhow, you would be going down the private cloud path which is really just a different way of selling managed services.


    The next key issue I would encourage you to consider very carefully is security. You need to ensure you're comfortable not really knowing what is happening in the background within the systems and with your data and I am speaking based on experience consulting for large companies. Large companies employ large numbers of staff to work in their organisations including their datacentres. I can say from first hand experience these large companies don't have a clue what is going on down at the engineer level, they might think they do but the reality is they don't and never will. What I can say as a consultant for many of the large Global firms I've been exposed to, the engineers who manage these types of systems and have access to client data are usually very well intentioned, have good morals and ethics and typically aren't even interested in customer data, but what I do get concerned about is the fact that issues and incidents, usually unintentional are covered up. I've personally witnessed critial systems in large enterprises (one of Australia's biggest banks as an example) was discovered to not have been getting backed up for years and when it was discovered the customer was not informed of the situation as it was simply covered up.

    Why Microsoft?

    At the end of the day, we had to make a choice as to who we would allow (notice I didn't say trust) to manage our data, backup and security. Through the history I personally have with current and former Microsoft staff and over 10 years working with their products, I'm personally satisfied enough to place this level of responsibility with them. For one, I've worked alongside countless numbers of Microsoft staff and engineers and have even worked alongside some of their Developers at various times, I was also once offered the opportunity to work for them. The culture in Microsoft is very strong and a lot of focus is applied to ensuring customers feel secure working with them and their data. Also the fact that I intimately know the products used to make up BPOS which include Active Directory, Exchange Server and SharePoint because you can purchase these products to install and run in your own environment and having done this many times in the past gives me as an engineer and a business owner the confidence I need to know and understand the mechanics of what is going on.

    Why Not Google?

    On the other hand, Cloud products such as those by the likes of Google, whilst these products work exceptionally well and have even been responsible for pushing email to new levels with new functionality, fact is very few people know the products inside-out. Very few people have ever had an opportunity to work with GMail and Google Apps at a detailed technical level (code and functional) and those who have are held to secrecy so who really knows how GMail and Google Apps work and what level of security is realistically built into these products. The fact that I can't purchase, install and run them on my own infrastructure means I can't build an understanding or trust in them, more importantly it means these products will always have a cloud of secrecy surrounding them. Not forgetting the recent events with Google's 'accidental' collection of data by their Street View cars tells me this company is not concerned about pushing the limits when it comes to privacy and clearly this is a culture embedded within the organisation because if a developer has invested time creating code to collect and record wireless access point information, that code would not have been easy or quick to create, it would have been relatively complicated and it would have required a considerable amount of time and effort be invested by a skilled developer as well as planning for the storage of the data which ran into the hundreds of gigabytes. All of these simple facts tell me it's more likely it was planned and it's likely it would have needed to have be approved by a manager (or managers) at various levels. I don't buy for a second this was an accident and it speaks volumes about the companies ethics and morals and I question what else they inadvertantly collected that they haven't yet disclosed or been caught with.

    The BPOS Exchange On-line Verdict

    A week in, the experience so far has exceeded all expectations. The performance and level of service from Exchange On-line has been excellent, we've never had any issues connecting, send or receiving mail and we're not getting any SPAM (though we weren't getting any SPAM before either). The fact that we don't have to worry about managing the infrastructure itself is a completely different experience to what we're used to, admittedly there are pros and cons to consider here though.

    Would I recommend this type of solution? I would but only to specific scenarios because I don't honestly think it's suited to everyone. In my opinion, Cloud driven solutions such as Exchange On-line are best suited to address companies with particular needs - such as businesses that want to run in virtual office spaces and businesses that don't have the need for in-house IT infrastructure. I know a lot of Cloud Computing providers will jump up and down and argue this until blue in the face, but my argument is if you have IT infrastructure internally and you only send some of your IT infrastructure offsite such as email with Exchange On-line, what are you really achieving?

    More Information

    If you're interested in cloud computing solutions such as Microsoft BPOS and T-Suite, additional information is available at the following sites:

    If you would like to discuss BPOS or any of the individual products such as Exchange and SharePoint for your business, contact our office on 1300 66 99 23.

    Posted: Jun 20 2010, 04:38 by Ben Fisher | Comments (0) RSS comment feed |
    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5

    Packaging Hardware Drivers & Vendor Supplied Installers

    Recently a client requested for some touch-screen software to be repackaged to enable silent installation onto their digital signage platform. In a nutshell, the touch-screen is a piece of hardware that once installed presents to the Operating System as a mouse and as part of the vendor supplied installation exe a driver is also installed. Upon initial investigation I quickly discovered the vendor supplied installer requires a system restart and if you follow the installation process documented in the setup manual it says to install the software prior to connecting the hardware, then once the hardware is connected you need to run through the 'Add New Hardware' wizard.

    Well, let me tell you this is an inefficient and more complicated process than it needs to be, most of which can be eliminated through Software Packaging (also known as Application Packaging) using products such as Wise Package Studio.

    In the case of the touch-screen software and driver I was able to prevent the reboot requirement as well as the need for running through the 'Add New Hardware' wizard. If you were to use the vendor supplied installer the four-step process would be as follows:

    1. Install software (Vendor supplied software installation)
    2. Restart system
    3. Connect hardware
    4. Install driver

    By repackaing the software installation into a custom Windows Installer MSI, I reduced the total number of steps down by 50% to the following two-step process:

    1. Connect touch-screen hardware via USB
    2. Install software (repackaged Windows Installer MSI)

    Because I used a method of what we refer to as 'driver injection' or 'preloading', the hardware can either be present (connected) or not. If the hardware is not present during the installation, the driver is preloaded into the driver store and when the hardware is connected the device is immediately initiated by the system and becomes ready to use because the driver is already present, similar to standard devices with built-in drivers.

    There are a number of factors to consider when repackaging software, in the case of the touch-screen software and driver it was a relatively small application and single driver. Eliminating the need for a system restart was achieved by two things - ensure the new services installed were started and; make sure the driver is properly installed, both of these were not adequately catered for in the vendor supplied installation. It didn't preload the hardware driver and it didn't start the services it installed, both of which are required to complete the installation process. The other issue I found was the device driver wasn't written correctly and the INF installer file needed some adjustment because it didn't point to the correct location for the driver .SYS file.

    Repackaging software offers great benefits over using the standard vendor supplied installers including the ability to customise the installation - such as add and remove features as well as streamline the installation and setup process. In many cases, smaller vendors - such as the case of Zytronic (maker of the Zytouch Touch Screens) as they don't specialise in software packaging it's common to find their software installers lacking features and capability and in number of cases I've seen vendor supplied installers which can only be described as downright rubbish - if not harmful to your computer.

    If you're looking for expertise to package (or repackage) your software installations, contact 2way Technology on 1300 66 99 23.

    Posted: May 10 2010, 15:20 by Ben Fisher | Comments (0) RSS comment feed |
    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5
    Filed under:

    Wise Package Studio 8 Released!!

    The leading Application Packaging software product, Wise Package Studio version 8 has finally been released. This new version brings a number of new features, the most important in my opinion is support for 64bit and improvements for packaging on Windows 7 or for Windows 7. You can get more information, including a Free Trial of the product here: http://www.symantec.com/business/package-studio.

    I suggest you keep a watchful eye on the known issues list:

    Known issues in Wise Package Studio 8

    Wise Task Scheduler issue. If you install Wise Package Studio Professional, and later add an Enterprise Management Server license, the shortcut to Wise Task Scheduler (an Enterprise feature) is not added to the Start menu.

    Altiris SVS Applet. The Altiris SVS Applet context-sensitive help does not work. By default, the help for the Altiris SVS Applet is installed in the C:\Program Files\Altiris\Software Virtualization Agent directory.

    SetupCapture. On a Windows 7 computer, SetupCapture hangs when capturing an .EXE with self-registering .DLLs if the Enhanced File and Registry Key Association option is checked on the General Settings tab.

    Firewall Exceptions. In Windows Installer Editor, on the Firewall Exceptions page, you cannot add a Firewall exception to a feature with a condition.

    Display Message action. In Windows Installer Editor, if you add a Display Message action in the Execute Immediate sequence, the message appears behind the progress dialog box on Windows 7 and Windows 2008 R2 computers.

    Media page. In Windows Installer Editor, on the Media page, if you select the Quickest option to create external CAB files, multiple cab files are not created for .WSIs.

    29212: If you uninstall Wise Package Studio and re-install it, the Altiris Software Virtualization Agent (SVS Agent) does not get reinstalled.

    • To prevent this problem, uninstall the Altiris Software Virtualization Agent before you uninstall Wise Package Studio.
    • If you uninstalled Wise Package Studio without uninstalling the Altiris Software Virtualization Agent first, then start Virtual Package Editor and you will be prompted to install the agent.
    Posted: May 06 2010, 16:49 by Ben Fisher | Comments (0) RSS comment feed |
    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5