Jump to content

kernelmart

Members
  • Posts

    14
  • Joined

  • Last visited

Reputation

10 Good

About kernelmart

Personal Information

  • Occupation
    IT Support Manager
  1. Hi, I had this bought to my attention yesterday. I asked user to show me her Android version, which is 11. From a quick google I found this: Why can’t I add my enterprise WiFi network in Android 11? The problem that many users will come across after they update to Android 11* is that the “Do Not Validate” option under the “CA certificate” dropdown has been removed. This option previously appeared when adding a new WiFi network with WPA2-Enterprise security. from: https://www.xda-developers.com/android-11-break-enterprise-wifi-connection/ I think I will have to work out how to do the certificate bit on the Ruckus controller now.
  2. This was Sunday 7th (South West of Sittingbourne, Kent): So I worked from home yesterday, but did dig myself out and go into school today.
  3. Hi, I use the SOLUS3 console to set up the patch to install overnight, normally 03:30. Avoids any exports and backup times for me. I also hope no one is likely to be using SIMS at that time.
  4. I have SIMS working on a 2016 VM ware VM (part of a farm), has RDSH and Licencing, SIMS runs as a RemoteApp program. Didn't do anything special for the install, just added the server to SOLUS3. Uses traditional profiles in the Users folder. This is with a 2012r2 Physical with Connection broker, RDSH, RD Virtualisation host, licencing and RD Web access. No apps on this one, just Hyper-V VM running a client OS.
  5. I couldn't see there were any customisations on my server (I'd inherited the network) and the OWA logon page was plain MS out of the box. I had a look at the web.config file (in Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa) and it had the date and time from when CU15 was installed. So I risked it and couldn't see any changes after. The other thing I did read though was make sure there a no certificate warnings on the server, expired, etc. before running the CU as apparently that can muck up the install. I ran this tool (its a powershell script that runs in the Exchange Management Shell) on my server before and after each step; https://exchangeanalyzer.com/ It gave me confidence I was going in the right direction. Thanks, Martin
  6. Hi, Mine was on CU11 till I upgraded in October. Due to the .net framework compatibility with CUs I went to CU15 first, .net Framework to 4.6.2 (from 4.6.1). Then installed CU18. With each step I let it all 'settle' at least overnight, before the next install. I did fortunately have a 2 week half term break to do it in. It was all a bit scary as each CU process is a full re-install. I hadn't touched Exchange since it was Exchange 2000 on NT4. I followed the steps in this guide; https://www.oxfordsbsguy.com/2015/12/20/exchange-2013-cumulative-update-installation-tips-best-practices/ I used the command line type for the AD schema parts. Then the GUI for the actual install. I also read around it all here; https://enterpriseit.co/microsoft-exchange/2013/upgrade-cu5/ and here; https://enterpriseit.co/microsoft-exchange/2013/prepare-ad-prepare-schema/ Thanks, Martin
  7. Hi, I had a read of the MS article for KB4038792 and followed a link to the "August 15, 2017—KB4034663 (Preview of Monthly Rollup)" https://support.microsoft.com/en-gb/help/4034663 Which has the following about half way down; Known issues in this update Symptom Workaround NPS authentication may break, and wireless clients may fail to connect. On the server, set the following DWORD registry key's value to = 0: SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\13\DisableEndEntityClientCertCheck Maybe that will help. Thanks, Martin
  8. Was actually further back than I thought, August 2014. We checked all of our 120 or so one at a time and according to the site, none needed doing. This was the URL; https://h30652.www3.hp.com/
  9. At my previous school I remember a HP recall/replacement process for clover leaf power leads for their laptop PSUs around 18 months or so ago.
×
×
  • Create New...