How to Uninstall Software With Winzero Schedule Service

To uninstall any Winzero software application that distributes the Winzero Schedule Service, requires a three step process

1) Remove folders and files from the remote computers.
2) Remove the Scheduling Service from the remote computers
3) Uninstall the software.

Remove any Remote Files

Select the computers to remove the Winzero remote files
From the Menu select Configuration
Select Remove Remote Files...

Repeat until all remote files have been removed from all computers

Uninstall the Winzero Scheduling Service

From the Menu Configuration
Select Manage Computer Schedule Service......
From the Popup Window Select one or more computers
From the Menu Select ACTION
Select Remove Scheduling Service

Once the service removal is complete double-Click the computer name to verify the service is not installed.
Close the ScheduleManager Window

Uninstall the Winzero Application

Exit the Winzero Application
From the Start Button Select Winzero
From the flyout select Uninstall
Select one or more Winzero Applications, from the list of Winzero Applications
Click Uninstall.

Previous Job is Running - Message

Bulletin: 010408

Software Effected:
SVRCompare, any Winzero Software using ScheduleManager

Issue:

I'm trying to run FILE-FOLDER collection with SVRCompare on remote servers NOW but it gives me this message: Previous job is running: XXXXXX I get this error too: \\XXXXXX Unable to Extract Application list

Solution:

SVRCompare uses a three method approach.

1 the collection
2 the import and comaprison
3 the comarison results report.

When you deploy the collection engine to the servers it will take from 40 minutes up to 16 hours to collect the information during the collection process. The time factor is dependent on the number of server objects, files, folders, shares, applications. During this process you can check the progress. Until the collection is completed you can not import the results for comparison until it is finished.

In the registry of the collection server there is a key that is monitored.

HKEY_LOCAL_MACHINE
Software\SVRC\State

if this key is not set to Completed (case sensitive) there is a job still running or a failed collection has occurred and the key was not set back to Completed.

Until this this key is in the Completed state you can not import results or move forward and you can not run or schedule a job again.

If you know that the collector on the remote server is not running you can reset this key with regedit to Completed and launch the job again.

Remote Computers Not Reachable by Name

Bulletin: 032007-1

Software Effected:
All Winzero Solutions Using ScheduleManger: DomainReconfigure, ServerMigrator, PasswordCopy, SVRCompare, RemoveUnknown

Issue:
When trying to add computers to the ScheduleManager in order to update or migrate workstations and servers, the list of available computers does not include computers that are known to be members of the domain.

Solution:
This issue may arise from 3 different possibilities:

The computer is not reachable by Name. DNS or WINS is not configured correctly at either the computer that is not appearing, the Domain Controllers of each domain where the migration is being performed or the computer used for the migration.

The computer is hidden from the browser
Routers are not broadcasting NetBios Names
Check that all computer DNS settings involved in the migrations are pointing to the target domain's DNS server.

If Windows NT4 is the source domain all computer WINS settings in both the target and source domain must be set to point to the WINS server in the Source domain.

If all computer DNS and/or WINS settings are configured correctly then Netbios Broadcasting is not occurring. To resolve this situation add or edit the LMHost file of each remote computer, the domain controller of each domain and the computer running DomainReconfigure to include the non visible computers, domain controllers and the DomainReconfigure computer.


Issue Solution Courtesy of the IT Staff at Charlotte State Bank(FL)

Winzero ScheduleManager Rights

Bulletin: 081707-1

Software Effected:
Software Using Winzero ScheduleService: DomainReconfigure, ACLReporter, ServerMigrator, PasswordCopy, SVRCompare, RemoveUnknown

Issue:
When sending an information collection or modification job to a remote server or workstation, the following error or errors are returned and the job is not completed:

- Can not import password list
- Can NOT locate Folder Permission File
- Can NOT Import Passwords from DCs or PDCs...
- Import File Not Copied

These errors occur after a remote job has been sent to a workstation or server and the job is launched correctly. The ScheduleService is running on the remote computer but the job did not collect and save the information locally on the remote computer.

Solution:
This situation occurs when the service account does not have adequate rights and privileges on the remote computer.

The service account must be a member of the local Administrators group of the remote workstation or server directly or indirectly through group membership.

The service account must not be the local administrator account. The local administrator account does not have rights back to the computer running the Winzero software. (If the computers are in a workgroup, then the Administrator account can be used; however the password for the Administrator accounts on all computers must be the same).

If Domain information is being set or retrieved the Service account must also be a member of the Domain Admins Group or Enterprise Admins group in each domain information is collected or set.

You can check the state and the properties of the Winzero Scheduler Service for a specific computer to determine whether or not the Winzero Scheduler Service is running, or is configured correctly to run on the specified computer.

In the Managed Computers frame of the Winzero ScheduleManager, double-click the computer.
The properties and a description of each property are listed in the Properties and Description frame of the ScheduleManager window

See SheduleManager Help file for detailed information.