October 27, 2015 at 5:13 pm
Hello,
I have had a look around the forums for an existing thread on this subject but have not come across one. I have been tasked with writing a Powershell script to automate the configuration of SSRS 2012, I need to automate it as I will need to run the script multiple times on a lot of servers for the foreseeable future.
SSRS 2012 will be installed already, but not configured, or configured in native mode with defaults, I will need to change the URL's of the report server and the reports, I will need to change the service account, the execution account, create a folder for the encryption key backup, then actually back the key up. And anything else that can be configured. At the moment I believe I do not have to worry about setting it up Sharepoint mode.
At first I thought I'd be looking at functions, but I think I will need to enter the information as parameters for the scripts. So a bit like a stored procedure with a few parameters that follow.
So here is the thing, I don't know any Powershell yet, this is my first of many adventures with it, what I need is someone to just tell me what it is I'll need to use, then point me in the direction of a place I can learn what I need to use to get the job done. I have about 2/3 weeks. I am looking at the SQL server Central Stairway series, which I will complete, but I think it will take me too long to get to where I need to be, and I'll run out of time.
I have to say I am really looking forward to learning Powershell.
Of course, if anyone has any other handy tidbits of advice, I'd love to hear from them.
Thank you for any help. Much appreciated.
Regards,
D.
October 27, 2015 at 10:29 pm
I would also suggest starting here in BOL: Scripting and PowerShell with Reporting Services. The basic gist of it all is there are no native PowerShell commands to interact or configure SSRS unless you are using SharePoint mode. What you are wanting to do is going to require a mix of things but most all of will be using WMI (get-wmiobject) in PowerShell.
A question on StackOverflow was asked and the guy provided a portion of his script but mind you it is not exactly what you are doing...but gives you an idea to get started.
Everyone has their on way and speed of getting familiar with something new, but I would say "about 2-3 weeks" is pushing it a little to understand, test, and troubleshoot this process for production.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
October 27, 2015 at 10:57 pm
Hi Shawn,
Thank you for replying, I'll check out the links you sent, much appreciated. Yes, I'd agree on the time frame, but then I always did like a challenge! :w00t:
If you don't mind, I may post what I have at certain stages to get some guidance. Thanks again!
Kind regards,
D.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply