Wondering if anyone has experienced this. I'm running Wise Package Studio 8.0 on a VMware Workstation (v 9.0.1) with Windows 7 Enterprise installed (Service PackĀ 1).

This VM does not have SCCM installed. I update it periodically by going to Windows Updates and applying the relevant security updates; otherwise, nothing on this machine changes.

I noticed about a week ago that when I run SetupCapture in Wise Package Studio, the SmartMonitor option is no longer available.

First I see this dialog, which is expected:

QMria2.jpeg


I then select 64-bit (not what's pictured, I know) and see this dialog, which is also expected:

PONFqB.jpeg


Next I see the following, which is not what I expected:

esgSZH.jpeg


Does anyone know how I can get SmartMonitor back as an option? Thanks.

4 Comments   [ + ] Show Comments

Comments

  • What happens if you select '32-bit Support'?

    Please remove the 'Scripting' tag from your post.
  • Works as expected: SmartMonitor can be selected if I choose 32-bit Support. I'll do some experimenting to see if that impacts any of my Setup Captures. Weird that it was an option for 64-bit but suddenly isn't.
  • I wonder if it was EVER an option. If you check the release notes for WPS8 MR1, which was the last release before the product was end of lifed (see here: https://www-secure.symantec.com/connect/forums/about-wise-package-studio-80-mr1-release), you can read that the capture engine was updated to include 64 bit snapshots, but Symantec explicity mention that the update did not include the process monitoring option (ie SmartMonitor).
    That is why the option is available for 32 bit captures but not 64 bit captures.
  • Ed, I'm certain I was able to choose it as an option. I just checked another snapshot I have on the same VM, which has AdminStudio's Remote Repackager, and the "Installation Monitoring" option, which I've always used in the past, is now grayed out and I can only select the "Snapshot" option, similar to what's happened in Wise.

    Since the only thing that's changed recently on this VM are Microsoft security patches (I manually install them every couple weeks to keep the machine updated), I'll look at those first to see if one of them caused this issue.
    • Are you able to roll back your VM to the pre-update revision? That would quickly confirm one way or another.
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity