Microsoft to deliver Microsoft Cloud from datacenters in Africa https://blogs.microsoft.com/blog/2017/05/18/microsoft-deliver-microsoft-cloud-datacenters-africa/
Source: Admin portals for Microsoft EM+S
So I naturally tried to access Win32_ComputerSystem WMI class using a Wbemtest but I was getting an Invalid class error
This looked like a corrupt WMI repository.
use CMD to run command
net stop winmgmt
select Yes or Y
sc config winmgmt start= disabled
for /f %s in (‘dir /b *.dll’) do regsvr32 /s %s
for /f %s in (‘dir /b *.mof’) do mofcomp %s
sc config winmgmt start= auto
give it a few minutes to complete then restart server.
VBS script can also be used this cover the entire C:\ drive
Create a RebuildWMI.vbs file then copy and paste the following script give it a good 15 minutes.
set osh = createobject(“wscript.shell”)
set fso = createobject(“scripting.filesystemobject”)
ret = osh.run(“sc stop iphlpsvc”,0,true)
ret = osh.run(“sc config winmgmt start= disabled”)
ret = osh.run(“sc stop winmgmt”,0,true)
bp = osh.popup(“Service stop returned ” & ret & “. Continue?” & vbcrlf & vbcrlf & “Ensure that WMI has stopped before continuing”,,”Continue?”,33)
if bp <> 1 then wscript.quit
if fso.folderexists(“c:\windows\system32\wbem\repository.old”) then
if fso.folderexists(“c:\windows\system32\wbem\repository”) then
set rfol = fso.getfolder(“c:\windows\system32\wbem\repository”)
rfol.name = “repository.old”
set rfol = fso.getfolder(“c:\windows\system32\wbem”)
for each fil in rfol.files
if right(lcase(fil.name),4) = “.dll” then
osh.run “regsvr32 /s “”” & fil.path & “”””,0,true
ret = osh.run(“sc config winmgmt start= auto”)
ret = osh.run(“sc start winmgmt”,0,true)
bp = osh.popup(“Service start returned ” & ret & “. Continue?” & vbcrlf & vbcrlf & “Ensure that WMI has started before continuing”,,”Continue?”,33)
if bp <> 1 then wscript.quit
set rfol = fso.getfolder(“c:\”)
Msgbox “WMI rebuild complete. Reboot server”
on error resume next
if lcase(fol.name) <> “system volume information” and lcase(fol.name) <> “recycler” and lcase(fol.name) <> “boot” and lcase(fol.name) <> “$recycle.bin” then
for each fil in fol.files
if right(lcase(fil.name),4) = “.mof” or right(lcase(fil.name),4) = “.mfl” then
osh.run “mofcomp “”” & fil.path & “”””,1,true
for each sfol in fol.subfolders
Run the script at every prompt give a good 15 minutes before it completes the process
have a look at windowsupdate.log file again and it should be sweet with no errors
The Image Factory has been re-worked and updated. It also has moved to GitHub https://github.com/DeploymentBunny/ImageFactoryV3ForHyper-V/
Concept and flow
The idea is the same, we use MDT, create refimages task sequences that runs without any questions. A PowerShell script will grab all enabled Task Sequences in a specified folder, create a VM for each of them. Grab the Bios Serial number from each om them, update customsettings ini with that information, start the VM’s (number of concurrent VM’s determine how many VM’s can run at the same time, wait until all VM’s are done and finally removes all VM’s for a cleanup process. You can run the script as is (if you store it in C:SetupImageFactoryV3ForHyper-V on you MDT server), or you can open it in ISE and run section by section to see what happens.
The XML file (C:SetupImageFactoryV3ForHyper-VImageFactoryV3.xml)
Is a control file for settings, pretty straightforward, just make sure…
View original post 128 more words
Take a look at @MS_SystemCenter’s Tweet: https://twitter.com/MS_SystemCenter/status/639088960518524928?s=09
Issue: Applications fail to start after installing Microsoft patch MS15-038 on Windows 7 64 bit devices when Data Loss Prevention Endpoint is installed.
It appears the issue relates to KB3045999 that has been pushed out to windows 7 64bit Devices which conflicts with McAfee DLP Endpoint 9.3.x.
I isolated the windows security Update to April Software Update Group
(Microsoft Windows 7 64-bit (32-bit is not affected)
After you install this security update on x64-based versions of Windows 7 that has McAfee Data Loss Prevention Endpoint (DLP Endpoint) 9.3.x installed, some programs may intermittently not start. When the problem occurs, you may receive an error message that resembles the following:
The application was unable to start correctly (0xc0000018). Click OK to close the application.
The affected programs include (but are not limited to) the following:
- Internet Explorer
- MMC-based applications
- Windows PowerShell
This problem may occur intermittently between restarts when the DLL is dynamically registered in different address spaces.
Example start up errors include:
- csc.exe- Application Error — The application was unable to start correctly (0xc0000142)
- iexplore.exe- Application Error — The application was unable to start correctly (0xc0000018)
- mmc.exe- Application Error — The application was unable to start correctly (0xc0000018)
- cmd.exe- Application Error — The application was unable to start correctly (0xc0000018)
Minimal, the issue is random, I managed to create the issue but a rebuild fix it.
Either remove Microsoft patch MS15-038 (Note Microsoft do not recommend that you uninstall any security update) or disable the affected components in DLP Endpoint.
Intel Security has released DLP Endpoint 9.3 Patch 4 Hotfix 25 to resolve this issue which need to be packaged and pushed out by DLP Administrator.
- See Microsoft article 3045999 for details on patch MS15-038: https://support.microsoft.com/en-us/kb/3045999.
See Microsoft Article for details on MS15-090: https://technet.microsoft.com/en-us/library/security/ms15-090.aspx.
- See McAfee Article for details : https://kc.mcafee.com/corporate/index?page=content&id=kb84538
Here are the steps for setting up a dedicated memory on a different drive:
1) Click Start, click Run, type Regedit, and then click OK.
2) Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
3) On the Edit menu, point to New, and then click String Value.
4) In the details pane, type DedicatedDumpFile, and then press ENTER.
5) Right-click DedicatedDumpFile, and then click Modify.
6) In the Value data box, type <drive>:\<dedicateddumpfile.sys>, and then click OK.
Note <drive> is a placeholder for a drive that has enough disk space for the paging file, and <dedicateddumpfile.sys> is a placeholder for the dedicated file and the full path.
7) On the Edit menu, point to New, and then click DWORD Value.
8) Type DumpFileSize , and then press ENTER. 18432
9) Right-click DumpFileSize, and then click Modify.
10) In the Edit DWORD Value dialog box, click Decimal under Base.
11) In the Value data box, type the appropriate value, and then click OK.
Note The size of the dump file is in megabytes, make this the amount of RAM plus ~5 to 10 mb.
12) Right-click DumpFile, and then click Modify.
13) In the Value data box, type <drive>:\<memory.dmp>, then click OK.
Note : <drive> is a placeholder for a drive that has enough disk space for the paging file, and <memory.dmp> is a placeholder for where the memory dump will be saved to.
14) Exit Registry Editor.
Note : If you have configured the page file as well as the memory dump on the same drive then make sure you have enough free space to accommodate the page file and also store the memory dump.
Take a look at @1E_Global’s Tweet: https://twitter.com/1E_Global/status/635467691021746176?s=09