Jump to content




hybrid

Administrators
  • Content count

    27
  • Joined

  • Last visited

  • Days Won

    6

hybrid last won the day on August 20

hybrid had the most liked content!

Community Reputation

9 Neutral

1 Follower

About hybrid

  • Rank
    Member

Contact Methods

  • Website URL
    http://peter.upfold.org.uk/

Profile Information

  • Gender
    Male
  • Location
    Hampshire, UK
  • Interests
    Passionate about building great things — code, writing, user experiences and more. Slightly obsessed with Macs, Linux, computer security and fonts.

Recent Profile Visitors

5,959 profile views
  1. Major forum software update

    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.
  2. 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: 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 the "Upgrades" classification: Get-WsusClassification | Where-Object -FilterScript {$_.Classification.Title -Eq "Upgrades"} | Set-WsusClassification -Disable [reference] Ran a Synchronize Software Updates from Software Library > All Software Updates in the SCCM console. Verified that the Upgrades category is off in both SCCM console and WSUS. Removed updates with PowerShell:$s = Get-WsusServer $s.SearchUpdates("version 1607") | Foreach { Write-Host $_.Id.UpdateId; $s.DeleteUpdate($_.Id.UpdateId) } $s.SearchUpdates("version 1511, version 10586") | Foreach { Write-Host $_.Id.UpdateId; $s.DeleteUpdate($_.Id.UpdateId) } Ran the WSUS Server Cleanup Wizard with only "unneeded update files" checked. Ran a Synchronize Software Updates from Software Library > All Software Updates in the SCCM console. Rebooted the SCCM/WSUS server. Altered the SUP configuration to add the "Upgrades" classification (Administration > Sites > (Primary site) > Configure Site Components > Software Update Point > Classifications) Ran the following SQL on the SUSDB: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) Ran a Synchronize Software Updates from Software Library > All Software Updates in the SCCM console. 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 the CCM cache from the Control Panel UI Deleted C:\~WINDOWS.BT from the client (from its previous upgrade attempt) Ran all the Action cycles in the Control Panel UI for the ConfigMgr client Went to Software Center > Updates > Windows 10 Feature Update... and ran the upgrade. The install process then proceeded, with Software Center then requesting a restart. The test client system then restarted into the WinPE part of the upgrade process (what formerly was the "Donut of Destiny" screen). The upgrade completely successfully!
  3. 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 the CCM cache from the Control Panel UI Deleted C:\~WINDOWS.BT from the client (from its previous upgrade attempt) Ran all the Action cycles in the Control Panel UI for the ConfigMgr client Went to Software Center > Updates > Windows 10 Feature Update... and ran the upgrade. We still see the same error on the client after the download and install attempt. Really trying to avoid a SUP reinstall if possible!
  4. 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 the "Upgrades" classification: Get-WsusClassification | Where-Object -FilterScript {$_.Classification.Title -Eq "Upgrades"} | Set-WsusClassification -Disable [reference] Ran a Synchronize Software Updates from Software Library > All Software Updates in the SCCM console. Verified that the Upgrades category is off in both SCCM console and WSUS. Removed updates with PowerShell: $s = Get-WsusServer $s.SearchUpdates("version 1607") | Foreach { Write-Host $_.Id.UpdateId; $s.DeleteUpdate($_.Id.UpdateId) } $s.SearchUpdates("version 1511, version 10586") | Foreach { Write-Host $_.Id.UpdateId; $s.DeleteUpdate($_.Id.UpdateId) } Ran the WSUS Server Cleanup Wizard with only "unneeded update files" checked. Ran a Synchronize Software Updates from Software Library > All Software Updates in the SCCM console. Rebooted the SCCM/WSUS server. Altered the SUP configuration to add the "Upgrades" classification (Administration > Sites > (Primary site) > Configure Site Components > Software Update Point > Classifications) Ran a Synchronize Software Updates from Software Library > All Software Updates in the SCCM console. I've run out of time to continue with this today, so I will update this post when we try to deploy again...
  5. 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:
  6. 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 deployment appears on clients (5.00.8412.1007 CCM client), and downloads the 2 GB or so judging by the time taken, but fails to apply. We never get to reboot into the WinPE(?) stage to perform the upgrade. The reported error code is 0xC180011 This is from $Windows.~BT\Sources\Panther\setupact.log: 2016-08-22 22:08:11, Info MOUPG RecoverCrypto: Entering Execute Method 2016-08-22 22:08:11, Info MOUPG DlpTask: Resetting action [0] progress start time. 2016-08-22 22:08:11, Error MOUPG RecoverCrypto: File is encrypted, but no key was provided. 2016-08-22 22:08:11, Error MOUPG CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118 2016-08-22 22:08:11, Error MOUPG CDlpActionRecoverCrypto::ExecuteRoutine(2465): Result = 0xC1800118 2016-08-22 22:08:11, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2101] 2016-08-22 22:08:11, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2100] 2016-08-22 22:08:11, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IDlpAction> > > >::Execute(441): Result = 0xC1800118 2016-08-22 22:08:12, Info MOUPG RecoverCrypto: Leaving Execute Method 2016-08-22 22:08:12, Error MOUPG CDlpTask::ExecuteAction(3243): Result = 0xC1800118 2016-08-22 22:08:12, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004] 2016-08-22 22:08:12, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2003] 2016-08-22 22:08:12, Error MOUPG CDlpTask::ExecuteActions(3397): Result = 0xC1800118 2016-08-22 22:08:12, Info MOUPG Waiting for actions thread to exit. 2016-08-22 22:08:12, Info MOUPG Actions thread has exited. 2016-08-22 22:08:12, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004] 2016-08-22 22:08:12, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2000] 2016-08-22 22:08:12, Error MOUPG CDlpTask::Execute(1631): Result = 0xC1800118 2016-08-22 22:08:12, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x3000] 2016-08-22 22:08:12, Info MOUPG DlpTask: Leaving Execute Method 2016-08-22 22:08:12, Error MOUPG CSetupManager::ExecuteTask(2067): Result = 0xC1800118 2016-08-22 22:08:12, Error MOUPG CSetupManager::ExecuteTask(2030): Result = 0xC1800118 2016-08-22 22:08:12, Error MOUPG CSetupManager::ExecuteInstallMode(690): Result = 0xC1800118 2016-08-22 22:08:12, Error MOUPG CSetupManager::ExecuteDownlevelMode(391): Result = 0xC1800118 2016-08-22 22:08:12, Info MOUPG Setup phase change: [SetupPhaseUnpack] -> [SetupPhaseError] 2016-08-22 22:08:12, Info MOUPG SetupManager::OpenOrCreateTask: Found task [Exit] in state [0x6] - Action [0xFFFFFFFF]. 2016-08-22 22:08:12, Info MOUPG SetupManager::OpenOrCreateTask: Deleting... 2016-08-22 22:08:13, Info MOUPG SetupManager::OpenOrCreateTask: Deleted task [Exit] 2016-08-22 22:08:13, Info MOUPG SetupManager::OpenOrCreateTask: Creating new task [Exit]. 2016-08-22 22:08:13, Info MOUPG CreateTask: Name = [Exit], WorkingPath = [C:\$WINDOWS.~BT\Sources], TransportId = [00000000-0000-0000-0000-000000000000], Flags = [0x0] 2016-08-22 22:08:13, Info MOUPG Finalize: Entering Prepare Method 2016-08-22 22:08:13, Info MOUPG Finalize: Leaving Prepare Method 2016-08-22 22:08:13, Info MOUPG DlpTask: Entering Execute Method 2016-08-22 22:08:13, Info MOUPG DlpTask: Transport not set. Skipping download phase. 2016-08-22 22:08:13, Info MOUPG DlpTask: Executing Actions... 2016-08-22 22:08:13, Info MOUPG Action execution thread timeout period: [1000 ms] 2016-08-22 22:08:13, Info MOUPG ImageExit: Initializing SetupResult: [0xc1800118] 2016-08-22 22:08:13, Info MOUPG ImageExit: Initializing Extended: [0x30002] 2016-08-22 22:08:13, Info MOUPG ImageExit: Initializing Scenario: [5] 2016-08-22 22:08:13, Info MOUPG ImageExit: Initializing Mode: [2] 2016-08-22 22:08:13, Info MOUPG ImageExit: Initializing Target: [C] 2016-08-22 22:08:13, Info MOUPG ImageExit: Initializing SQM: [TRUE] 2016-08-22 22:08:13, Info MOUPG ImageExit: Initializing PostReboot: [FALSE] Even after clearing the CCM client cache, SoftwareDistribution folder, deleting the software update package from the CCM server and downloading and deploying it again, we see this issue across each of the several systems we have tried. Any further insights would be greatly appreciated! Is there anywhere else we should be looking on the server to do with decrypting the .esd?
  7. New site logo!

    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 'favicon' should now also render beautifully in several different sizes if your browser is able to take advantage of that, too. We'd love to know your thoughts on the new logo, and hope it helps keep Windows-Noob fresh and with the current developments in the Windows world!
  8. 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 needs to be installed as a service, with an extra piece of software called VBoxVmService. Here's how to set it up: 1. Install VirtualBox as normal, and create your new virtual machine as normal as well -- running through the install process. Once everything is running fine, you'll probably want to enable VRDP/VRDE on the virtual machine's settings, so you can access it over RDP. Once VirtualBox is running as a service, you can't use the VirtualBox application to control the virtual machine, so VRDP is the ideal solution. (Or for Linux guests where you only need access to the command line, configure an SSH server for remote login on the guest before you move to the next step). 2. Install VBoxVmService into C:\vms. We first need to edit the INI file in this folder with the information to install the service: [settings] ServiceName=VBoxVmService VBOX_USER_HOME=C:\Users\Administrator\.VirtualBox RunAsUser=.\Administrator UserPassword=enteryourpasswordhere RunWebService=no PauseShutdown=5000 [Vm0] VmName=name of the vm in VirtualBox ShutdownMethod=savestate AutoStart=yes Substitute in the VBOX_USER_HOME with the .VirtualBox folder in the correct user's home directory, as well as the RunAsUser and UserPassword directives, and set the name of the target virtual machine in the VirtualBox app in VmName. You can also add additional [Vmx] sections after [Vm0] with other virtual machines to start when the machine boots. When you are happy with your configuration, from an Administrator-enabled Command Prompt, run: C:\vms\VmServiceControl.exe -i to install the service. Once the service is installed, you can remove your user password from the INI file, as it is saved in the Service configuration. If the RunAsUser you have entered does not have the Log on as a service right, you need to grant that right to the user, or the service will not be able to start. The easiest way to do this is to go to Start > Run > services.msc, find VBoxVmService and edit it. On the Log On tab, re-enter the user's password and click OK. You will get a notification that the relevant right has been granted. 3. Now, you must reboot the computer before attempting to start the service for the first time, or it will be unable to locate the VMs. 4. Upon reboot, the service should start (subject to the 'Automatic (Delayed Start)' delay) and your VMs will be started upon boot. You may wish to edit the Service to set the startup type to Automatic to avoid this delay. At any time, you can uninstall the service with: C:\vms\VmServiceControl.exe -u Also, if you want to make any changes to the service, you must edit the INI file, uninstall the service as above, reboot, reinstall the service and reboot again. It is annoying, yes, so hopefully you don't have to make changes too often. That's it! We now have the VBoxVmService starting the selected VirtualBox virtual machines at system startup, without the need for anyone to interactively log in.
  9. site will undergo an upgrade today

    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.
  10. site will undergo an upgrade today

    I have clicked edit and then re-saved that post as suggested to fix the BBCode. It seems to have worked. Please let us know in this thread of any other posts that need this attention.
  11. Playing with Server 2008 R2 and Exchange 2010!

    1. XistEnCe

      XistEnCe

      How is that working out for you?

      Going to try that setup myself, when the new disks arrive :)

  12. Hi everyone!

    Thanks. Yeah, sorry, I meant to say been playing with Server 2008 R2 -- I obviously failed to mention the 'R2' bit! Right now the only 64-bit machine that I personally have access to and is in a suitable state in terms of disk space is my MacBook Pro. So right now I'm actually already virtualising Windows Server 2008 R2 inside VMware Fusion on that machine. Does Hyper-V have any benefit over using a different virtualisation solution like VMware, as I am now?
  13. Hi everyone!

    Hi everyone! I'm Peter Upfold, a.k.a. hybrid and I've been a long time member of Windows-Noob's sister site Linux-noob for many years. I really enjoy playing around with technology all across the spectrum -- from Apple stuff, Linux stuff and Windows and Microsoft technology too. I recently went ahead and purchased a TechNet Standard subscription, because I want to become more familiar with Windows, particularly the server side of Microsoft's offerings which can be difficult to get familiar with if you don't have access to the software! So far I've been messing around with Windows Server 2008 and 2003 and Exchange 2010, but the TechNet subscription means that I should be able to get familiar with all sorts of other interesting products too. So I might be asking a few questions here and there as I play around and run into the inevitable problem or two. Hopefully in time I can answer others' questions too.
  14. wanted: site logo !

    It started showing up correctly for me after clearing my cache, quitting the browser and then re-opening it. It now works for me -- so eventually it should show up everywhere.
  15. wanted: site logo !

    Updated 'halo' version! (difficult to see the halo against the background below, but it works well in the browser). Caching of the old favicon may be an issue -- seeing if I can get the new one to show up! windows_noob_orb_favicon_withhalo.ico
×