Earlier last week I ended up making a new pa system for Bucketworks. Now what most people will not realize is everything at Bucketworks is hacked to gather and this is no different. I was asked to make a low power radio system for notifying people within Bucketworks for people at the door and other uses, seeing we would need to file for an fcc licence i decided to go another route and the Bucketworks pa project was born.

during our wondering around at Bucketworks we (paul,eli,and I) have come across manly things one of them things was an old pa speaker and I got to thinking does it still work? I ended up wiring one up to an amp, we found in the basement along with a old audio mixer seen below after finding out we had a bad 1/4″ cable.

and low and behold it worked.
https://www.youtube.com/embed/Lehy4tTpVCg

The next step was to figure out where all the rest of the speakers were located and where to run the wires back to the server room where we were going to store the audio equipment. we ended up finding a total of 5 speakers wired them in and played some Pandora over the new pa system. I had to modify a cable to go from the “server” to the audio board.

I then set to making the Bucketworks pa bot. This bot is a windows client that logs in into an irc channel and organically just sent text to a text to speech function over the sound board. I expanded it to authenticate, noaa weather warnings, play music, tell the time and a few other functions.

After showing it to a few guys we ended up hearing this and we all started laughing.

and the Bucketworks pa project was complete.
If there is any interest i will upload the code if it is wanted.

Want to learn how to build a cantenna?

Stop in at our meeting next Friday to find out!

So if your like most admin’s you and have a bunch of Support staff some times its just easier to give them access to hyper-v then to have them wait for the admin to complete a simple task (ex.make a snapshot). The only issue with this is the fact they can do things we don’t want… for instance turn a machine off reboot change settings like nics along w/ creating new machines. So i went looking and apparently there is a way to restrict this so this post goes to show how we can.

Assigning Rights to hyper-v
Open mmc.exe

Click file then add/remote snap-in

Select authorization manager and hit add and ok

Then right click on Open Authorization Store….

Select XML file then hit browse

Goto \\Server_name\c$\ProgramData\Microsoft\Windows\Hyper-V\ and select InitialStore.xml

Then hit ok

Role Assignments
Select the Role we want to assign in this case its Administrator

Right click and click assign User and Groups then select from Windows and Active Directory…

Enter username you want to assign rights to. And hit ok

That user will now have admin rights.

Creating New Role Definitions
(what rights does this group have?)
Expand intialstore.xml -> Hyper-v services ->Definitions ->Role Definitions

Right click Role definitions and click new role Definitions

Then enter a name and click add…

Select Operations tab

Then add what rights you want that role to have by checking the checkbox and hitting ok, ok.

Now that we have a new role definitions created now we need to create role assignments see role assignments Section.

Role Assignments
Right click create new role assignment

Select what role that’s been defined

And hit ok

Now we need to add user into this group see Role Assignments

Apparently Microsoft did not include WDS manager with there server 2012 RSAT (Remote Server Administration Tools) once again…
to enable remote wds control place the fallowing script in a batchfile and run batchfile.bat wdsservername

copy \\%1\c$\windows\system32\WdsMgmt.msc c:\windows\system32\WdsMgmt.msc
copy \\%1\c$\windows\system32\en-US\WdsMgmt.msc c:\windows\system32\en-US\WdsMgmt.msc
copy \\%1\c$\windows\system32\wdsmgmt.dll c:\windows\system32\wdsmgmt.dll
copy \\%1\c$\windows\system32\en-US\wdsmgmt.dll.mui c:\windows\system32\en-US\wdsmgmt.dll.mui
copy \\%1\c$\windows\system32\WdsImage.dll c:\windows\system32\WdsImage.dll
copy \\%1\c$\windows\system32\en-US\WdsImage.dll.mui c:\windows\system32\en-US\WdsImage.dll.mui
copy \\%1\c$\windows\system32\wdscsl.dll c:\windows\system32\wdscsl.dll
copy \\%1\c$\windows\system32\wdstptc.dll c:\windows\system32\wdstptc.dll
copy \\%1\c$\windows\system32\WdsTptMgmt.dll c:\windows\system32\WdsTptMgmt.dll
copy \\%1\c$\windows\system32\en-US\WdsTptMgmt.dll.mui c:\windows\system32\en-US\WdsTptMgmt.dll.mui
copy \\%1\c$\windows\system32\wdsmmc.dll c:\windows\system32\wdsmmc.dll
copy \\%1\c$\windows\system32\en-US\wdsmmc.dll.mui c:\windows\system32\en-US\wdsmmc.dll.mui
regsvr32 WdsMgmt.dll
regsvr32 WdsTptMgmt.dll
regsvr32 WdsMmc.dll

once you do its now possible to remotely manage wds servers in your network by typing WdsMgmt.msc in search.