Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


hybrid last won the day on April 8 2020

hybrid had the most liked content!

Community Reputation

10 Good

1 Follower

About hybrid

  • Rank
    Windows-Noob Server Administrator

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Hampshire, UK
  • Interests
    Passionate about developing a deep understanding of the whole technology stack and using technology to make a positive difference to people. (he/him)

Recent Profile Visitors

7,961 profile views
  1. Smoothwall Express will be OK for labs, but the folks at Smoothwall haven't updated this "community" edition of their product since 2014, in contrast to their commercial offerings (still based on open source, although I think they need to update that page). I'd be worried about security with a firewall product this out-of-date for any production use! I'd recommend something like PFSense that gets regular updates! 👍 I've used PFSense on Hyper-V in some production environments for a while — it works beautifully! Niall has pointed out on YouTube that there are post-install u
  2. A quick update on this — it seems likely that something is wrong with our SQL Server Cluster. I spun up a new one-node Failover Cluster to test this, and found that the PIPE\winreg endpoint did work on this new cluster. I think that makes it fairly clear that this should work and that the problem lies with our SQL Server cluster and not with ConfigMgr. So, we will look at trying to fix the SQL Server Cluster!
  3. Don't try this at home -- obviously this is thoroughly unsupported. I was able to use API Monitor to set a breakpoint on the RegConnectRegistryA API call being made by smsexec.exe and cmupdate.exe and patch the machine name that it's trying to connect to the registry at to point at DB-Cluster instead of DB-Cluster-SQL. There were several calls to RegConnectRegistryA which caused the breakpoint to be hit. Each time, I expanded the string argument for lpMachineName and updated the value (fortunately a shorter string) to point to the correct machine. The prereq check is now h
  4. Possibly similar... the SMS_HIERARCHY_MANAGER's hman.log says: The following port [1433,4022,] tcp firewall exception not active on SQL Server [DB-Cluster-SQL.*****]. At this exact time, the smsexec.exe with that same thread ID from hman.log above uses the named pipe to try and evaluate the firewall options on the wrong hostname again, just like the prereq check.
  5. A little background. We have: a single site server (Windows Server 2016 1607) running the various CM roles (CM 1906, site version 5.0.8853.1000) a two-node Windows Server 2019 cluster hosting SQL Server 2016 for the site database server The database cluster has a shared hostname and IP address for the Windows cluster computer object itself (DB-Cluster.our-domain) and another shared hostname and IP address for the SQL Server role (DB-Cluster-SQL.our-domain). We've not had any previous issues with this setup for the last few updates to ConfigMgr, but when attempting to upg
  6. I have upgraded Windows-Noob.com today to the latest and greatest version of the IPS Community Suite. We are now on version 4. Among all the other features, this should significantly improve your experience when accessing the site on mobile devices thanks to the responsive theme. If there are any issues that you notice, please post in the Suggestion box.
  7. We have followed the new steps in KB3194588 and, in particular, the new database steps as @RLC-Andrew points out: declare @NotNeededFiles table (FileDigest binary(20) UNIQUE); insert into @NotNeededFiles(FileDigest) (select FileDigest from tbFile where FileName like '%14393%.esd' except select FileDigest from tbFileForRevision); delete from tbFileOnServer where FileDigest in (select FileDigest from @NotNeededFiles) delete from tbFile where FileDigest in (select FileDigest from @NotNeededFiles) It works now! I repeat myself from above, but for clarity here is what we did, in full:
  8. I've now also: Created a new servicing plan "Windows 10 Education 1607 Servicing Plan". It uses a new deployment package. Clicked Run now on this new Servicing Plan. Verified that the content download is in progress: Verified that the two expected upgrades (en-us and en-gb that matched our rule when previewed) are "Downloaded". (Not "Deployed" yet) Got impatient and ran a Software Update point synchronisation to try and get the deployment to appear. Verified that the two expected upgrades are now "Downloaded" and "Deployed": Went to a client that is in the deployed collection and cleared t
  9. Here's what we've done: Removed the test deployments of the Feature Update Removed the Servicing Plan associated with those deployments (so there are no Servicing Plans) Removed the Deployment Package that Servicing Plan was attached to Deleted the folder associated with that Deployment Package from the disk Rebooted the SCCM & WSUS server Altered the SUP configuration to remove the "Upgrades" classification (Administration > Sites > (Primary site) > Configure Site Components > Software Update Point > Classifications) Altered the WSUS configuration to also not include t
  10. Indeed: our deployment is for the Feature Update to Windows 10 Education 1607. The en-us and en-gb versions of that SKU are the only upgrades downloaded. Our machines believe they are on en-us language pack(?) (although we have UK regional settings). Our Servicing Plan rule: The results of previewing this: Our deployments to two collections:
  11. We are experiencing an issue trying to install the 1607 Feature Update using a Windows 10 Servicing Plan in ConfigMgr CB (5.0.8412.1000). We have a simple single server SCCM infrastructure. The required KB3159706 has been installed on the server, and the additional steps in "More information" at the bottom of that KB article have also been carried out. We've cleared the download of the Feature Update and downloaded it again after verifying the steps. Both the WSUS site and the Configuration Manager site in IIS have the .esd mimetype set to application/vnd.ms-cab-compressed. The deploym
  12. Some of you may have already noticed, but we have a new logo here for Windows-Noob.com. Since our previous 'lifering' style design with the four Windows colours was introduced, a new era of Windows and its visual style is upon us. The red, green, blue, yellow flag is now the Microsoft logo, rather than just for Windows, while the OS itself gets the blue, leaning 'window' design. So, to reflect this new era that Windows 8 and Windows Server 2012 brings, Windows-Noob's logo now echoes the new design, while staying true to its 'noob' roots with the "just hatched" design. The '
  13. While this isn't strictly 'Microsoft Application Virtualization', I came across a problem where I wanted to run VirtualBox on a Windows Server 2008 R2 host, and have the virtual machines started automatically when the machine boots. (Hyper-V is great, I'm sure, but we went with VirtualBox for this particular solution as we were running a Linux distribution that is very picky about its virtualised hardware requirements, and is unfortunately very old -- Cisco Eagle Server <pdf link, 1.5MB> for teaching the CCNA courses). In order to get the VirtualBox VM to start upon boot, it need
  14. Apologies to anyone who has recevied these phishing/spam PMs. I have banned the 'Alibaumaro' member concerned. Please feel free to delete any of these messages you have received.
  • Create New...