Thinking about replacing vb login script with Desktop Central configuration (anyone have any experience/currently do this)?

I currently use a vb login script (like I'm sure many folks do), to accomplish a variety of tasks during login. I know that Desktop Central can do some/all(?) of the items my script does but I'm wondering if anyone has current experience and can comment on any pitfalls.

My current script:

Maps a few network drives (one based on username, one depending on whether a person is a member of a specific AD group, the other a general everyone gets it drive).

Runs a batch file that overwrites a local file on our PC's. (I've been meaning to investigate setting the script up to only overwrite the local file if the server version is never but I just haven't gotten around to it).

Finally it generates a pop up that asks if the employee wishes to fill our their timesheet. If they say yes it launches a url taking them to our timesheet website.

Can the desktop central agent do these things? These can be user or machine based configs? Is it worth it to move from a vb script to the agent?

In addition I'm curious about how printer installs work via configurations as well.

Thanks for any info folks can provide....