Posts made by Mike Davis

@scottalanmiller You might also like "The New Global Student" by Maya Frost. I read it because she mentions Rotary Youth Exchange, but it lines up pretty good with what you're doing.

yes, like this:
http://www.axis.com/us/en/products/axis-q1604-e
I should add I'm in upstate New York, so our winter may be different than yours..

@JaredBusch said:

That is just a silly thing to say. PoE and PoE+ require, per the IEEE standard, category 5, but is still allowed to be ran on category 3 for lower wattage workloads.

I haven't installed many PoE+ cameras and have only had those running less than a year. Do you have a number of PoE+ cameras running on CAT5? Longer runs? I'm wondering why the camera company I was dealing made such a big deal about 23 guage CAT6 for their cameras. Maybe because it had a heater?

I'm running all CAT6 for premise wiring. I might still use some CAT5e patch cables, but those are easily enough swapped out. I have heard of some PoE+ cameras burning up when run over CAT 5 cable. I don't want to have to go and rewire a building because I saved a few bucks on the cable.

@JaredBusch Thanks for the explanation. That makes sense.

@JaredBusch I just did it this morning on a box. I didn't try to install the .msi before running dism /online /enable-feature /featurename:ServerCore-WOW64
I did notice I didn't need a reboot, so I figured that someone ran it before me.

I also ran runprereqchecks.exe /s and didn't get prompted, so I know that step works.

Before step 5, you might have to:
dism /online /enable-feature /featurename:ServerCore-WOW64

Then cd \smsa\windows\preReqChecker
and run:
runprereqchecks.exe /s

that will prevent the warning later on.

Both roles are on the same box.

@Dashrender Yes, the terminal server is in the terminal server license servers group, and it's not a domain controller. In addition I followed these steps: (from https://support.microsoft.com/en-us/kb/2030310)

Use the Delegate Control Wizard to add the permissions to add read\write permissions to the terminalServer attribute or to the Terminal Server License Server attribute of the “user object” by the Terminal Server License Servers group. To do this, follow these steps:
Right-click the domain in Active Directory Users and Computers, and then click Delegate Control.
In the Users and Groups dialog box, click Add. Type Terminal Server License Servers, and then click OK. In the Users and Groups dialog box, click Next.
In the Tasks to Delegate dialog box, click Create a custom task to delegate, and then click Next.
In the Active Directory Object Type dialog box, click Only the following objects in the folder. In the list, click User objects (the last entry that is in the list), and then click Next.
Do one of the following, according to the operating system that the domain controller is running:
For forests that are running Windows Server 2008 or newer Schema:

In the Permissions dialog box, make sure that only the General check box is selected. In the Permissions list, click to select the Read and Write Terminal Server license server check box, and then click Next.
In the Completing the Delegation of Control Wizard dialog box, click Finish.

They are not being denied in either case. Just events in event viewer. The error is:
The Remote Desktop license server cannot update the license attributes for user "admin" in the Active Directory Domain "contoso.com". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "contoso.com".
If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.
If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.

@Dashrender So you have to switch the licensing mode of the server to match your licenses?

Once I was able to see the configuration, it became clear and I should have noticed it in the first picture. It was pulling from the temp pool in the per device mode, and the paid licenses were in the per user mode.

With that said, if I just flip the mode, I get a different event in event viewer, and it doesn't pull a new temp license.

Doing:
net stop winmgmt
winmgmt /salvagerepository
net start winmgmt

fixed the problem of not being able to open Remote Desktop Session Host Configuration. I can now see the licensing mode is Per Device. I'll see if it's still throwing an error when I log back in.

I should also add when I tried to launch Remote Desktop Session Host Configuration to see which licensing mode is configured, it errors with "Unable to complete operation:Not found"

It's 2008 R2

@Dashrender Isn't that what the first picture is? Where do I find that?

I think something else is going on.
Eventvwr shows the error, but under licensing you can see the licenses. Any ideas?

@scottalanmiller If you haven't read it already, you should read "The Egyptian" by Mika Waltari while you're still in Crete.

@Joy said:

Rich Dad Poor Dad -Book by Robert Kiyosaki

I recommend that book a lot.

Monoprice.com search for hook and loop:
http://www.monoprice.com/product?p_id=5828
you can get it in different colors if you want to separate out your voice and data, by floor, etc.