Bozteck VNCScan Community

i would like a simple way to manage printers for add and remove.

also a simple way to add/remove/update shortcuts

Next would be a software depolyment for adding apps

a way to edit group policy

Thanks for considering

still need a way to run some inventory reports..

For printers it really depends.  If you're talking about locally connected printers, there are scripts.  For connections to network printers, those need to be made on a per-user basis.  You can create login scripts or if one of your Domain Controllers is Windows 2003 R2, you can use the new Print Management tool to set printer connections via Group Policy.

I posted a simple script for creating shortcuts in the Scripts forum here.

There's a lot to Software deployment.  If you're trying to install software from MSI files then Group Policy is the simplest way.  Other than that, there are a number of products that specialize in that area that will deal with lots of different installers.  This is such a big area that it would be hard for VNCScan to include robust deployment functionality.  Better to get a specialized program.

The Group Policy Management console is great, but it's not installed by default.  It's available from Microsoft at http://www.microsoft.com/downloads/details.aspx?familyid=0a6d4c24-8cbd-4b35-9272-dd3cbfc81887&displaylang=en

For inventory I usually tell people to look at Spiceworks (www.spiceworks.com).  It's free software that does a very complete inventory.  It's not the best there is, but you can't beat the price and it does a fairly good job.

We just replaced our domain controllers with two Win2K3 machines, so I'll have to try the Print Management in group policy.
Also, Microsoft is supposed to be releasing a completely redone Group Policy editor based on the DesktopStandard tools and I'll have to try that. It's free for those with Microsoft SA agreements.
We've always ran scripts that add a printer "globally" so it shows for all users.
I have examples of that in the Scripts forum.

We use KIX scripting for this.  I think that we need to add that as a list of available scripting languages along with the CMD and VBS selections.  Until then, you can simply add the kix32.exe with your script in the editor.

---

Thank you,

Steve Bostedor