@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:

@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:

I'm looking for an option similar to User Configuration>Preferences>Windows Settings>Files where you can copy a file from a directory directly to C:%userprofile%\Desktop, but I want to be able to include a custom made .ico.
....
Any experience or ideas?

Now if we have figured out that this is a database file, not a front end application component that is stateless, then the need and reason for copying the files makes sense. It's a stateful backend file called a front end, but that isn't a front end (facepalm)...

Then a script is one option that will be decently easy. Or a tool like Salt or Ansible will do this easily. GPO probably can, I just don't know the mechanism that would normally be used outside of just calling a script.

Yea, I'm just going to run a script for the xcopy and then configure the GPO to point to it's location as @Dashrender suggested earlier. Makes sense, and seems pretty straightforward and easy.

They meant source code, but whoever wrote it doesn't know what source code is and it makes no sense.

What they should have said is...

Install from TarBall without a Repo

Or CentOS via RPM, Ubuntu via DEB, etc.

Gotcha. Thanks, I'm almost a pro at this already.

The boss made an additional domain (.net) in the forest after I made my second Exchange Server on our current domain (.org).

They have a relationship, but don't replicate.

I'm trying to add mailboxes for users on the .net domain's AD.

I've added .net to the Accepted Domains via Exchange Admin Center, and ran /PrepareAD on .net DC. Rebooted.

I can make any user in the .org AD a .net address, but cannot get the "existing users" to populate from the .net AD when creating a mailbox.

What am I missing here?

@Supreme_Overlord said in Good Specs to Build a Gaming PC (asking for a friend):

@scottalanmiller okay, didn't know if that would help with being able to perform faster. What size SSD would be good then?

Modern games are starting to get big. Anyone who is a serious gamer needs to have at LEAST 2TB, especially going into the next gen consoles, you'll be deleting games just to make room for more as they come out. It's something I hear about with all my friends on PS4 who still have the 1TB factory HDD. The SAMSUNG 1TB 860 EVO is a pretty decent SSD, with a price point around $160 you could double up eventually, or save a few bucks to get the 2TB right off the bat. If the benefits of SSD don't sway you, then a 4TB HDD can be found for like $100.

As the title suggests, I have recently been having a hell of a time getting policies to apply in a timely manner.

I ran gpresult /z and it returned our backup DC instead of the primary.

So I start researching how to possibly point Group Policy at the main DC and come up with either "it can't be done", or you have to adjust the "weight" of the DC's and make the main one "heavier", which I mostly understand, but won't explain because the Registry key change they suggested doesn't exist and the walkthrough was from 2013 so it possibly doesn't apply.

So I'm in AD Sites and Services and see that our backup DC is set for replication intervals of 180 minutes (explains the less than timely policy updates). And now I'm finding and reading all I can on how to configure and understand AD Sites and Services.

I'm wondering, should my main DC and backup DC be in the same "SITE" (Default-First-Site-Name) or is them having an IP Inter-Site Transport really the only important detail here? If, from what I've read so far, the Inter-Site Transport is responsible for replication, then I feel like moving the backup to another "SITE" would be the right move as they will still be set for replication because they are still present in the Inter-Site Transport. However, after doing this nothing has changed and gpresult /z still returns backup DC.

Is AD Sites and Services even what I should be looking at?

I wasn't getting what I needed from my lesson and turned to google to grasp a better understanding of Subnetting. I'm reading this article : https://support.microsoft.com/en-us/help/164015/understanding-tcp-ip-addressing-and-subnetting-basics

About halfway down the page under Subnetting it explains that "The subnet mask 255.255.255.192 gives you four networks of 62 hosts each. This works because in binary notation, 255.255.255.192 is the same as 1111111.11111111.1111111.11000000. The first two digits of the last octet become network addresses, so you get the additional networks 00000000 (0), 01000000 (64), 10000000 (128) and 11000000 (192)....Using a subnet mask of 255.255.255.192, your 192.168.123.0 network then becomes the four networks 192.168.123.0, 192.168.123.64, 192.168.123.128 and 192.168.123.192. These four networks would have as valid host addresses:

192.168.123.1-62
192.168.123.65-126
192.168.123.129-190
192.168.123.193-254

Remember, again, that binary host addresses with all ones or all zeros are invalid, so you cannot use addresses with the last octet of 0, 63, 64, 127, 128, 191, 192, or 255."

---

What I don't understand is why they are excluding 63, 127, and 191? I've converted those to binary and they aren't all 1's or 0's

63=00111111
127=01111111
191=10111111

In fact, 64, 128, and 192 aren't all 1's or 0's either, are they incorrectly explaining leaving room for a switch or DC or is there another reason to exclude those numbers?

Edit: my binary conversions needed work, but I fixed that