Alot of subtle changes being made as we move forward. A few products are being piloted and some issues being sorted out.

Pilots:

PC Anywhere is being rolled out today or tomorrow. This will give us a look at how stable the product is compared to Remote Desktop in the DS 6.9 products(Which was a wonderfully reliable product except on multi monitors). Working ok in the lab so far.

Do What?

The Software manager. This is one ridiculous product. it's a library of your installer files(Which means it keep s acopy of everything to do not a whole lot with, wasting disc space?) The software you import in here and add command lines in the package tab can be replicated to the Package servers, but some how this storage space isn't available as a Package server source? Also if we went through the time to import the command lines for the product, how come you still have to go back in and set the newly imported product as Manager? Why would anyone go through the...

I just finished a remote session with a customer that found a computer from the database that is not sending data back.

I had received the log files yesterday and the log viewer was all red and blue. Upon inspection it was clear that the agent COM components are not working (not registered or unregistered), so no basic inventory, client session management or sub-agents could perform their normal tasks.

Still the agent was getting it's policy file from the server, but not being able to do anything with the given policy (given its state).

We checked the computer Windows logs and found nothing interesting in there, so we crafted a SQL query to detect other computers with similar issues:

select 
       distinct(s.ResourceGuid),
       i.Name, MAX(_eventtime) 'Last config request',
       MAX(s.ModifiedDate) 'Last Basic Inventory',
       MAX(s.createdDate) 'First inventory',
       DATEDIFF(d, max(s.modifiedDate),
       MAX(c....

Items completed:

3 SMP servers, 1 parent, 2 child with hierchy completed.

SQL maintenence plan created per Symantec recommendations.

AD import completed.

Subnets manually created(We are using the 8 scheme which would have been tough to import)

Tested PCAnywhere functions, decent product, not very good at screen aspect ratios for such a mature product. Very bare bones?

Only issues are: 1 server had to be respun in VM and rebuilt becuase of various strange errors with SMP agent. Also some Java oddities when importing OS files, which thankfully can be bypassed by simply pressing cancell to the credential challenge(This was on XP and 7 desktops with the Symantec's proposed GP configuration in palce. But that error still persisted, attached is the photo of the error, on an XP machine you can press cancell and continue with the file upload).

The design of the product still irks me a bit for the options on Site Servers. Even with fiber...

A few days in to the migration, have some questions came up. So lets go through it.

Our infrustructure is more like 1 huge building than 80 separate sites. The availability of having fiber connected to all the sattalite campuses means we can centrally manage as if they were in the same building. The problem is SMP isnt really designed for that kind of infrustructure. And the few issues we encountered are:

1. The technicians cannot manage the infrustructure in real time from 1 console. The amount of our clients meant we had to use hierchy, which means teh Parent server sees things later(Synch schedule). While all synched machines will be on the Parent server, any new clients will take 24 hours for the Parent console to see. Which means no OOB deployment from the parent Console.

2. Replication of packages maybe required as Task Servers, which means we would have to replicate our packages atleast 5 times(5 Task Servers). We dont need that as our San can handle the...