My notes

Monthly archives for August, 2010

Apply .WIM with SCCM: Windows cannot verify the digital signature for this file

Aug17
2010 Leave a Comment Written by Oddvar

I have had this issue at a customer. We could not find out why the deployment stopped at various times. We did not find any pattern at all. The Advertisment status reported this error messages:
The task sequence execution engine failed executing the action (Apply Operating System) in the group (Install Operating System) with the error code 2147942977

Action output: *********\SMSPKGD$\***00114\ before releasing

Released the resolved source ********.*****.******\SMSPKGD$\***00114InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia ), HRESULT=80070241 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,373)

WIM error:C:\Program Files\********\*****.***

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Error: 80070241; Source: Windows)

Unable to apply (0×80070241)

Installation of image 1 in package ***00114 failed to complete..

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Error: 80070241; Source: Windows). The operating system reported error 2147942977: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

And also this message:
The task sequence execution engine failed execution of a task sequence. The operating system reported error 2147942977: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

I then started investigating the servers event logs. I found the following event in the application log when this happened:

It turned out that the SCCM was installed on a x86 server and therefore SQL could not get enough ram to do its thing. Therefore when we deployed a machine the deployment was interrupted, because the server was forced to unload due to memory pressure.

So a solution is to move the installation to a X64 server with X64 version of SQL to get more memory. Or tune your current setup.

UPDATE: I have also seen this error if you are trying to deploy while the OS image is beeing distributed to another distribution point. (Install pending)

Rating 3.00 out of 5
Posted in SCCM

Setting up FileZilla FTP Client as an External application in mRemoteNG

Aug10
2010 Leave a Comment Written by Oddvar

In order to launch ftp client from mRemote you can do this to define it as an external application:

Arguments start with a <space>.

Rating 3.00 out of 5
Posted in Tools - Tagged , , ,

Deploy Office 2010 with integrated Language Packs

Aug10
2010 6 Comments Written by Oddvar

For many this is basics, but for some reason I seem to forget this from time to time. Therefore I have chosen to create a blog post to remember the steps.

Create the Office 2010 package as you normally would. Copy the Office CD to a share and add it as a New Package.
Remember to create the MSP file using the setup.exe /admin switch. These are the settings I use normally:

Microsoft Outlook 2010 – Account Settings – Exchange – Automatically Configure profile
based on Active Directory Primary SMTP Address = Enabled


Microsoft Outlook 2010 – Account Settings – Rss Feeds – Turn of RSS Feature =
Enabled


Add Property HIDEUPDATEUI = TRUE


Set Outlook Profile to Modify Profile

I normally use a KMS server for key management. But this depends on the environment. Then you save these changes to office2k10Silent.msp and save it in the root of the office folder where setup.exe is located. In order to integrate the language pack as part of the setup I then copy the needed folders from the language pack cd:

Every folder that is needed ends with the name of the language. (in my case .nb-no)
I then copy the config.xml file from the enterprise.ww or the proplus.ww folder to the same location as setup.exe is located. This name of this folder varies from the version you are deploying. Then I edit it like this:

<Configuration Product=”ProPlus”>
<Display Level=”none” CompletionNotice=”no” SuppressModal=”Yes” AcceptEula=”Yes” />
<AddLanguage Id=”match” ShellTransform=”yes”/>
<AddLanguage Id=”en-us” />
<AddLanguage Id=”nb-no” />
<OptionState Id=”OfficeMUI” State=”Local” Children=”force” />
</Configuration>

Notice the match switch. When that is set the installation will find out if the OS is English or Norwegian and install the Office GUI with that language.
We then need to specify how to run the installation. I create a program inside the office 2010 package that runs the following command:
setup.exe /adminfile office2k10Silent.msp
That’s it. The config.xml file will be read because it is in the root of the directory. Microsoft documentations states that MSP files and updates can be put in the updates folder of the installation. This works great. The only thing I have noticed is that office
completely installs the entire office suite and then runs the .MSP file and “peels” of the options that you have chosen to exclude.

Happy deployment!

Rating 3.00 out of 5
Posted in Deployment, SCCM - Tagged , ,

Translate my page

    Translate to:

    Powered by Google Translate.
    translation services

Stats

Visits today: 1
Visitors Online: 0