• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 458
  • Last Modified:

Windows 2003 VSS

I would like to enable VSS onthe server, I found this link.

We have over 1000 users and I would like to know how to deal to the second half part mentioned in the link regarding how to setup workstations to use VSS.

<<<The other thing that you must do is to configure your workstations so that they can access the shadow copy files. To do so, you must create a network share on your server that allows clients to access the server’s %SYSTEMROOT%\TWCLIENT\X86 folder. >>>>>

3 Solutions
You can use group policy to deploy the client to the workstations and install it automatically.

That's what I did. I don't have as many users as you but it has worked fine for me.
This portion of article is badly written.  That location contains the previous versions client.  You could either share this location directly and manually install client, share directly and access via software installation or copy the twclient.msi to another location and deploy from there.
jskfanAuthor Commented:
hstiles ,

do you have any link for a better article.
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

jskfanAuthor Commented:
Naser72 ,

I am not sure the link above talks about w2003 server VSS. Correct?
jskfanAuthor Commented:
brwwiggins ,

can you be specific? Can you show me how you did it?

I appreciate it.
dang it, i typed up a long response and don't see it here....grr

here it goes again...shorter version

I chose to assign the client to the computers in the domain simply because all users will need the client regardless of the machine it is on.

I put the VSS client (msi package) on a share that everyone can access. I then go into AD Group Policy and create a new Policy. In the new policy I went to computer configuration ->software settings, right click on software settings and select new -> package. Here is the tricky part. When you browse for the package you need to be sure to browse using the path that the clients would use. For example if the MSI is on \\server\vss then that is how I would browse to the file instead of going to d:\tools\microsoft\vss or whatever. The path you browse with is what will be handed out to the clients in order for them to find the package.

I left the package as "assigned" to the machines and then linked the group policy to the specific OU. You can decide where to link the policy based on your architecture and how many people would be trying to access the package across the network.

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now