CHiLL

With the move to Click to run, does that mean the version available on VLSC will be the same as the version that will become available via Office 365 downloads? Or will there be differences like there are between Office 365 and 2016 ProPlus?

We found the problem with using user groups was it doesn't restrict the usage from the logon screen.

I have a Veeam backup job that backs up a server as reverse incremental and a 30 day retention period. I also have a backup copy job that backs up the same server and is configured with 2 restore points and a 30 day schedule. For the backup copy job, after two months I have three files in the directory; .vbm, .vbk and .vib, I know that these files are the metadata, full backup and incremental backup respectively. If I wanted to manually copy the backup copy job files to the cloud...do I need to copy all three of those files? If I excluded the .vib, would that mean I lose the data from the latest backup?

I don't think it can be removed, but it can be disabled by denying 'Everyone' read access to it. My GPO is configured in: Computer Configuration > Policies > Windows Settings > Security Settings > File System. I created two entries for: %SystemRoot%\System32\EaseofAccessDialog.exe %SystemRoot%\System32\Utilman.exe I added the 'Everyone' group in and set a deny on full control for 'Everyone'. If you need to then access it (to revert settings or whatnot), you have to browse to the machine using File Explorer from a remote machine and manually change the file permissions on the 'Everyone' group.

Thanks for the reply. We use follow-me-printing for staff and direct printing for students and found that without the deletion, it would leave 'ghost' printers in the list for the next user. So if a member of staff logs onto a computer, they get the Photocopier virtual queue. When a student logs on, they get the direct queue added specifically for the room they are in (item-level targeting based on machine OU). However without the delete item, students were also seeing the Photocopier queue when they shouldn't.

Anyone got any ideas?

So I have a Printer GPO that contains 32 printers, configured in the 'User Configuration > Control Panel Settings > Printers' section. Ordering the printers by 'Order', the first is 'Delete All'. Then the printers are listed in the order they were added (there are item-level targeting rules that also apply to target certain users, groups, computers, OUs, etc). However, I've found that when students log into the library, they are not receiving a printer. Upon checking the GPResult, I can see that the policy first added the printer (item 18 in the list) and then ran the 'Delete All', (first item in the list). The reason we have the 'Delete All' option is to remove ghost printers, such as when a member of staff logs onto a student computer and gets the Photocopier added, the next student to log on would also get Photocopier, which we don't want. Is there any reason why it's not processing it in the correct order? How can I prevent this from happening? Here's a look at our list: [ATTACH=CONFIG]50133[/ATTACH]

Thanks for the responses. I now have the CPUs set in what I think is a more optimised way.

So for overall performance without over-committing the cores (as Domino was suggesting), what would be best? I've been comparing it to standard desktop CPUs, where I have 1 CPU with 4, but I guess it doesn't work that way with vCPUs!

Thanks for the replies. I think I'm getting confused with vCPUs. When assigning CPU resources to a VM and I want to use say 2 vCPUs, how do I configure that in vSphere? I can see the CPU drop down with 1-32 as an option and I can see cores per socket, which has a multiple of the selected CPU value. What do I set these to to get 2 vCPUs for that VM?

This is why I've created this thread, to help me understand the situation. I've read through that thread and I'm still none the wiser on how to allocate the CPUs. What's the best way to spread the CPUs without one VM using one whole physical server's worth of allocation? Here's our CPU performance for out cluster over the past 24 hours (with practically nobody on-site). [ATTACH=CONFIG]49895[/ATTACH]

Thanks for the reply. Whilst I had the servers down, I decided to take the following approach: Servers with <=8GB RAM - 4 CPUs and 4 cores. Servers with >8GB RAM - 8 CPUs and 8 cores.

Unfortunately not.

What's the best practice for RAM allocation when it comes to vSphere HA / failover if one host dies? At present I have ensured that each host is using HALF OR LESS of it's installed RAM. That way should one host fail, it can fail-over to the working host and have no performance impact. However that leaves a lot of unused RAM on each host. If I increase the RAM usage per host, then should a host fail, the working host would become over-committed. I'm wondering what other people do in this type of scenario?

We have 2x HP DL360 Gen9, which both have 2x Intel Xeon E5-2630 v3 CPUs and 192GB RAM per host. The hosts are both running ESXi 6.7 (coupled with VCSA 6.7). Since we have scheduled downtime, I'm looking at the resource allocation for our servers and have managed to get our RAM allocations sorted. However I'm not sure how to assign the CPUs. When modifying the CPU values, what's the difference between CPU and Cores per socket? Could someone recommend the CPU allocation for the following types of servers? Server RAM allocation: File server with shared applications - 4GB Backup Server - 8GB Biometrics server - 4GB Domain Controller - 8GB Management server (includes Impero Server, DirSync and SalamanderAD) - 16GB SIMS - 16GB Web Server - Spiceworks - 4GB File Server - Students - 12GB ADFS Web Application Proxy server - 4GB Old CMIS Server - 8GB ADFS FED Server - 4GB RDS -24GB RDS Gateway - 4GB Web server - Home Access Plus - 4GB SCCM Server - 16GB Print server - 4GB File Server - Staff - 12GB What sorts of CPU allocations (both CPU and core per socket) should I be setting for the above servers?

Turns out that in our scenario, the Intel drivers were not being installed correctly by SCCM. Therefore we were using the very basic drive (or the default one that Windows 10 installs), which didn't include the WOL features. After deploying out the driver package to the clients, WOL started working again.

Bah, that's annoying. Thanks anyway.

We have a datastore that is about 5.5TB in size and only 1.3TB of that is in used as data drives for some of our VMs. Since there is over 4TB free (which has been free for pretty much 3 years) I was wondering whether it'd be possible to create a network share on this datastore so that I can utilise the space on these disks, instead of using other NAS devices? Is this possible?

I've PM'd you with a screenshot of our Core Switch routing config. If you wouldn't mind taking a glace, that'd be great.

I have amended the OP to reflect the change. Smoothwall's external interface is definitely pointing to the router's IP address.

It does have internal and external network interfaces. I've just checked and the external interface already has it's default gateway set as the IP of the router, so my diagram is incorrect regarding the route from the Smoothwall.

That's correct. I don't want to risk causing a loop. So for example let's say I make that change and set 0.0.0.0 to route to the Smoothwall, the Smoothwall will have to then push traffic back through the Core Switch to get to the router. The Default Route would keep trying to push everything back to the Smoothwall would it? Including it's own traffic?

We have had Smoothwall installed recently as a VM to replace RM's SafetyNet but have ran into some issues which I think are network related, specifically regarding the default route. So our network prior to Smoothwall being installed was using RM's SafetyNet with transparent proxy enabled and the traffic flowed as follows: With the Smoothwall, the network is the same, however we disabled RM's SafetyNet, disabled transparent proxy and blocked all traffic that does not come from Smoothwall's IP address. We use GPO or manual proxy settings to redirect all HTTP/HTTPS traffic to the Smoothwall VM on our one of our ESXi hosts, so the HTTP/HTTPS traffic flows as follows: I've attached a (poorly) hand drawn diagram showing our current layout. However we've found that non-proxy aware devices or applications are taking the default route out to the Internet. As the traffic has not come from Smoothwall, it does not actually get to the Internet. Is there any way of making all traffic flow through the Smoothwall VM and then to the Internet? P.s, We're using a HP ProCurve 5406zl core switch.

I've just raised this issue myself through the WJEC E-Marker support emails and received a reply. They have simply forwarded me a message that they've received from DRS: I've forwarded this onto Smoothwall, who I'm hoping will provide some insight on whether we can get this working.

Thanks for the replies, it's made for an interesting read. Maybe I'll just stick with Vmware and save the hassle!