-
Posts
9,168 -
Joined
Content Type
Forums
News
20th
EduGeek EDIT Conference
Blogs
Everything posted by Steve21
-
Thanks, Sorry should have said before but on that first screen if you click the advanced button what’s that message say? As normally it’s say something like server can’t prove its print-server as it’s issued from blah etc Steve
-
Make SIMS and/or HyperV server unavailable without turning it off?
Steve21 replied to enjay's topic in How do you do....it?
If it’s just SIMs on it you could just stop the SQL service and disable it so it won’t restart That way you can still access the server if needed even without SIMs being active Although that is assuming nothing else is running from it still Steve -
Windows 2022 Network Services Restart Issue
Steve21 replied to discoveranother's topic in Windows Server 2022
That shouldn’t be any different, we use SET in 2019 (was in 2016 server) My point with the DNS side was the only time NLA changes profiles is when it detects the DNS Name response on the NIC and if it’s not a domain one it won’t set the domain profile in NLA (say for example the service starts up too slow) But that’s even if it’s just 1 drop it’ll then cache that response until you restart The reg key just tells it to keep trying until it finds a response as it’s always expecting a domain response from DC Steve -
Yep that’s as expected. Papercut generates it based on server name by default, so if you want it FQDN you need to change it to that as per their documentation - https://www.papercut.com/support/resources/manuals/ng-mf/common/topics/tools-ssl-key-generation-recreate-self-signed.html The only other thing I guess you may have done previously, is changed the server name in papercut config to be the FQDN rather than server name, and you might have overwritten that with an upgrade. In Papercut admin custom options what do you have the server name set as now? But from what you’ve explained so far, nothing seems wrong as that’s working as expected Edit - just saw your reply, can you upload a screenshot of the browser error with url and the Cert name showing on the actual Cert (from the browser NOT what you deploy as these could be a different Cert) without seeing what you see hard to tell what you’re getting Steve
-
Windows 2022 Network Services Restart Issue
Steve21 replied to discoveranother's topic in Windows Server 2022
That’s generally a DNS issue as it only checks once for the domain connection and then caches the information until next restart (effectively what you’re overriding by forcing it to restart) You can make a change to registry to make it keep retrying until it finds it though, which would remove the task workarounds (until the long term issue is sorted as to why it’s not detecting domain etc) On one of the machines you get it happening to, add HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters With a DWORD named AlwaysExpectDomainController and set it to 1 Steve -
Adding a Cert locally that’s still for the wrong name wouldn’t resolve the wrong common name unless I’m missing something. The error is invalid common name, not trust related The way you’re talking about would be if it’s a non trusted locally generated Cert etc that the machine doesn’t know about? Steve
-
What name is the Cert using? As it wouldn’t normally cover an IP and name st once so one of those errors would be expected. Only what is covered under the common name would apply and show as non-error But in terms of you’re comment about the Cert being in trusted root do you mean on the printnserver? As papercut has its own Cert store and doesn’t use MMC style ones Steve
-
Windows 2022 Network Services Restart Issue
Steve21 replied to discoveranother's topic in Windows Server 2022
I think you’re mixing up a few things here as you’re not supposed to manually restart NLA etc. what’s the actual issue you’re getting for you to try that? But in terms of actually doing what you’re trying both NLA and NLS spawn svchost.exe processes, while they’re running you can’t stop the services, and both services will automatically restart their svchost.exe if you close it after a few seconds So if your every quick in killing both svchost.exe and stopping services it’d do what you want. But It’s not at all designed to do that Steve -
Not sure if you’re doing what I did originally but there are two config tools One won’t let you pick it as it’s not for volume licensing etc If you go to https://config.office.com sign in and go to device configuration and create new configuration you get all the options (with a huge licensing disclaimer warning on the device based licensing ) Steve
-
You should be able to just remove it as a pre-provisioned app during deployment, like you would to remove xbox etc using MicrosoftTeams as the app name Steve
-
If you're after proper sunlight coverage you'll need a lot lot more than that Think last time I looked for monitors to support sunlight direct (outside screens etc) it was 500~ for "daylight" and 1000~ for "sunlight" as a real minimum really Is this more just for daylight reflections though, or are you talking direct sun etc? Steve
-
They’re sold in increments of 5 but it’s one item covered, they have a nice calculator to check https://www.veeam.com/pricing-calculator Steve
-
I’d say they have the licensing wrong for you for a start VUL are per VM so if you only have 4 it would only cover 4 VMs Compared to 6 sockets on the 2nd option But personally always go for sockets, they’re much better value normally, so much so that Veeam are stopping selling new socket licenses on July 1st and only supply VUL (both are supported still just not new sales). And if you suddenly want to add 10 more VMs you’re fully licensed compared to paying for more VULs Steve
-
I mean by default, if you assume AX real world wise will probably max at 4~ Gb, you now have 133Mb per machine (based on 30 connections before phones), compared to 1Gb cabled in etc (and that 133Mb is assuming you can actually supply the AP with 4Gb connections, if you're only using a 1Gb to the AP that's even slower) Then taking into account the things like losing ability to WOL etc Personally I wouldn't think about it in any state unless you "realllllllly" can't have cables Steve
-
Have you got a picture of the one with the cutout, can open up the boxes we got and check it tomorrow, no harm done if not Steve
-
0YF1JW Is the same code we have for 740s one from last year so either the XD is different or it may be you Steve
-
Do you know what code they are? We got some new Dell servers in last year and can’t stand the CMAs so they’re still be sitting in their boxes somewhere but not sure if the 640 & 740 standard version would be the same as the XD type Steve
-
Isn’t that only if it can’t auto detect the subscription though? There was a url provided few weeks back that you had to make sure was open/accessible else that screen appears Steve
-
I’ll ask the obvious, but are you sure it isn’t 4GB? Thought they used to be tiny just for restore/format/encryption tools etc Steve
-
Unless there's something specific you want in A5 like Teams as PBX etc (as well as a few others to make the total worth it), it's generally cheaper to A3 and then add on an item or two separately if there's something you want like Defender (or add a few A5 to specific staff etc) Steve
-
Normally with the old equallogics they also use about the equiv. 2 disks for logs/snapshots/eql database/reserve/config etc. So in a normal EQL 24 bay with RAID6, you'd end up with 20 + 2(logs etc) + 2 hot-spares, meaning the 20 usable disks would be about 16.4TB~ I know in some editions of SAN HQ you used to be able to change the above, but generally that's as expected in terms of outcome Steve
- 4 replies
-
- dell
- equallogic
-
(and 1 more)
Tagged with:
-
Not sure if it’s still the same as thankfully been a while since I had to use cubase, but we found we had to manually wrap the certificate install for the driver before the elicenser so that when the software ran it didn’t ask the uac prompt to accept the publisher Might be worth trying to see if that still works Steve
-
You shouldn't be getting any cert error if you're using a server name unless something is wrong, as it should match your trusted domain and just connect. The reason for getting it via IP is your 10.10.10.10 etc wouldn't match the SSL response of server.domain.com etc When you get the cert warning using the server hostname, if you click view cert what's the error it says on it? as that should help narrow down your issue Steve
