During the install of SMC it would be nice to have more customization control over Symantec Management  Console. Such control would be to include or exclude features for Linux, Mac, or Windows. If you select not to install such features then the agents, reports, and other such tools should not show up on the console.

I think it would be very beneficial to have other items that can define what machine an app is provisioned to, rather than simply the user id.  In an environment when people do switch machines from say a headquarters site to a DR site and you only want the streaming/virtualized app available at DR.  You could set up 2 streaming environments, but then you also have to manage 2 environments.  If you set up a nice load balanced system that covers many of your sites, you can ...

Hello, Except I miss something or trip/trick for this, we can not capture a new layer or update an existing, if this layer has a "high" dependency to another. eg. if you create a layer for your SQL express, and you want to create another layer for your DS installation: You need the SQL running, to install your DS. But you cannot do that because to capture a "new application", you must deactivate ALL your existing layers ! I also try to create an "empty layer", ...

Really needs to be built into an enterprise level tool like this, we are using the update synch trigger originally created by Condorman and have issues with that not working quite as expected. It would be great if full Active Directory synchronisation was built into the product

My issue with it is simply how messy the "Applications" list is in "Computer Properties". A base Windows instalaltion will show such things as: Address Book, Branding, DirectAnimation, IE40, IE4Data, IE5BAKEX, and every single KB article on the system. It also shows multiple entries for patches i.e. MSXML4, "Security", and many, many more. For Mac systems you get every little component like "X11", "Time Machine", ...

I'm running Patch Management Solution 6.x and think it'd be cool if there was some automatic mechanism to stage then deploy the patches on different schedules to different collections.  For awhile now, per our internal desktop patch management agreement, I've been testing the updates on 2 or 3 of my PCs when Microsoft's "Patch Tuesday" rolls around and if I don't encounter any problems, I'll deploy to desktops in just my department (IT) a week later ...

We use a service account to install applications. This means we have to ennter the account details for every task in every job we create. Not so bad as you go alog but if we need to change teh password we will need to renter it twice for each task which can be a real pain if you have one or two hundred jobs with multiple tasks and also filters. The account information used to join the PCs to a domain is stored in the system surely it must a simple task to store account information centrally ...

A lot of people create custom reports that could be useful to other people, but it is difficult to find them on Connect.  When someone creates a report and puts it on Connect, they could be tested and approved by Symantec and then added to a specific location that could then be accessed from the NS Console.  This would be an easy way to share "good" reports and could save time for a lot of us.  You would also know what kind of reports people are needing and they ...

I highly sugest Altiris integrate in the inventory the following information, seems not currently collected by default from Altiris CMS 6 or CMS 7 (and that is a shame) Device enumeration string (PCI/VEN_8086&DEV_1234) Device driver file, Version + name + editor name... I was so despite to see not included in standard Altiris inventory 7 !