Discussion Locked

Is It Wise To Use WinBatch As Part Of An I.T. Enterprise Solution

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello everyone.
I've been wondering as to whether or not WinBatch, a scriptiong tool, should be used as part of an enterprise solution. I have someone in my organization who is pushing WinBatch saying that it is the tool for use in I.T. Infrastructure solutions for things like software distribution. As a result, we now have I what I think is a very unprofessional looking tool with this GUI that has some buttons on it to do some things. The tool is involved in working with background services and downloading software to PCs, scheduling the arrival of software, etc.

The thing that bothers me is that solutions like this I have normally seen implemented with larger professional tools like something from Microsoft Visual Studio using C# or Visual Basic. Those tools have some very nice GUI capabilities and certainly some commercial output capability.

When I see what we have in WinBatch I don't get that same impression. I am somewhat concerned that maybe WinBatch is not the proper tool to create something that runs over 10,000 computers of which some are involved in mission critical operatoins.

Unfortunately, I don't know that much about WinBatch so I'm bringing this story here to see what others may have to say about using it. Is it only good for small projects or its ok for big ones? What is the story? Thanks in advance.

6 replies

by dloegering

We use winbatch for our IT only programs. There is no real reason we do not do other programs for our end users with it. It is solid for the right type of programs. We use it to register users IP addresses on the network in their logon script. We then have a winbatch program that looks up the users IP so we can shadow their desktop when they have user issues. We have used Winbatch to move mail around an Exchange 5.5 server as well.

by windowsmt60

I know this post is somewhat dated... but I have been using WinBatch for 13 years.

I am a qualified network engineer and systems architect. What I am NOT is a programmer. I understand syntax and how to read code, but I do not write code. Despite this, I have been able to create some very professional looking applications and implement them for common tasks.

While WinBatch itself introduces some overhead in the way of DLLs that need to reside on the machine in order to quickly process scripts (if you choose not to compile them), what it gives you is flexibility to quickly and efficiently get tasks done, including scheduled runs, updates (especially flat file updates) and it will encapsulate VBScript and other languages fine if you know what you are doing.

When you refer to it not looking professional, this may be due to either your programmer not knowing HOW to make it look ANSI standard, or you have the actual product installed as opposed to just making the DLL calls.

All in all, I have used KixTart and WinBatch for scripting and both have their strengths, but WinBatch gives you incredible flexibility (especially when combined with the compiler) to offer solutions for non-programmers to perform automation.

I used Winbatch to update 102 routers automatically with new configs. When ever I wanted a refresh, I put in a new dated file into my update directory, called out to the routers and updated the confg files. It also backed up the existing files, did versioning, and monitored upstates. There is no doubt that C# and VBScript allow you to do some nice functions with RegExp and such, but Winbatch gives you those functions through wrappers, and there is little in the way of automation I haven't been able to do.

I am obviously a proponent of WinBatch, but I am not discouraging the use of other languages. I am just saying don't underestimate its power. I think you are more than likely fighting an inexperienced programmer, not the product.

MT

by irelandc

I have been using WinBatch for the last 5 years in our IT shop to do a multitude of automated tasks that would otherwise require manual intervention.

Prior to that, all of our scripts were in Windows batch files and VB scripts. I have converted most of our old scripts over to WinBatch because it easy to expand on the functionality and do more with the script than was ever possible before.

We don't use it as a software distribution platform however. It is used as an installation wrapper, to make the installation entirely automated and hidden from the end user.

And for our technicians, most of the heavy lifting in terms of PC setup and management have been shifted to WinBatch programs which ensure that all tasks are performed uniformly and correctly across all of our systems.

So, as an easy to use, IT centric, "programming language", it runs circles around other more esoteric languages more meant for application development and games.

As for the question about the professional look, the dialogs created by WinBatch with the buttons and text entry boxes and such are the same common Windows dialog boxes we've all seen. Any unprofessionalism would have to be the scripting behind them and not the appearance of the dialogs themselves.

by slayer_

We have some ancient WinBatch scripts that read data from the LOS and flips through the GUI screens of a banking system and inputs the data for the user. It's extremely legacy code and is officially unsupported, but we haven't replaced it yet cause after all these years, it still works perfectly. If Winbatch is safe enough to handle millions of people's money, it is certainly safe enough for a small 10k computers.

by derrick.anderson

We support 20 and going up to 30 + thousand machines.
We have used Winbatch since 2005 to present day, for almost everything.

We made templates for everything - which are easy to make, like:
* login scripts
* packages
* custom support utilities
* Custom Organization Dialogs
* reporting
* etc

We use it to wrap vendor media (Package) and deploy via SCCM
The UAC was easy to bypass when Vista came out; to alleviate the cert and virt issues; but, that also depends on the security expectations \ policies your organization decides to go with.

It also has custom dialog wizard to create the GUI and the Winbatch studio to code and compile it.

Their forum and resources are alwasy there to help with your coding challenges and is the best and always quick to respond - for the most part its always free and online.

If i had my way i would use it always - but now that virtualization is getting more popluar, we are now looking at AdminStudio to create virtualized snapshots and deployed via Application Virtualization Client (very steep pricing (almost a million for licenseing 30000 machines to use the Flexera Admin Studio produced packages))

im checking with winbatch today to see what their response is to the virtualization trend that is up and comming - more to follow

This discussion is closed to new replies.