We currently have a vb script that is running locally on every server we build. The script was created a long time ago and we are unable to update/edit the script. When it deploys, it has hard coded port 1433 for the ADO connection. Unfortunately
that port will be closed and none of the data will be allowed to transfer.
I'm looking to create a tool that will all for the data to be pushed over web services. I know nothing about development other than some basic html/ classic asp scripting. I do have some powershell experience and was able to create a script using
the port 1433 to call specific wmi information from the server and then using the ado connection over port 1433 insert data, however since this port will be closed, not sure what our next step is in creating a longterm solution.
Environment:
over 200 Domain servers, mainly 2008 R2 and 2012 R2.
Need to obtain all sort of data from the server and then send to a sql db.
I was thinking sometype of web services / RestAPI but again, I know nothing just what I have read and it looks like the right path but not positive. Since I'll be learning this from scratch, hoping to find the best way moving forward so we can get
a good long term tool in place.
Please let me know if any more data is needed to help guide me in the right direction for replacing our current system.
Thanks,
Serge
Jr. Admin
