Office issue after sysprep

superlulu · 31 Jan 2017

Hi everbody,

I've deployed for my compagny Win10 with custom image on acer pcs. I've used sysprep for install programs and customize profil. Thanks Kari for this thread:

https://www.tenforums.com/tutorials/...e-sysprep.html

All is fine. But I have a new problem on these pcs. If I install Excel 2010 or Word 2013, these programs work not fine.
Excel says that there's not enough memory and i can't open files on my network, Word says that it can't find temp folder. They work only if i run in administrator privileges.
If I try with Office 2007 I have same issues.

If I try to enter to audit mode, install office, then enter to oobe, I have same issues.

It's Windows 10 Pro 1607

thanks for help...

superlulu · 31 Jan 2017

I have an other image, just before sysprep.
If i install office, do not use sysprep, join my computer in domain and install for my user, it works...
Problem come only if i use sysprep and install office after

Kari · 31 Jan 2017

I've never seen Sysprep causing any issues with Office. I myself run Office 2016 on a heavily modified and customized setup, with relocated Users folder and user profiles, generalized with Sysprep, Office installed in Audit Mode before sysprepping. Absolutely no issues.

Could you please copy your answer file, remove all personal information from that copy replacing it with X's (company name, possible product keys and so on), zip it and attach to your post.

Office memory warnings are quite common issue, here's Microsoft's support article with various stuff you might be interested to test: https://support.microsoft.com/en-gb/...rrors-in-excel

Kari

superlulu · 31 Jan 2017

thanks Kari for your answer.

In fact, PCs are in production, with an old office suite (office 2000) . But I have to install office (Excel 2010 and Word 2013) in these pc on production. So after sysprep. Not before.

Here is my answer file, only used for copy profile:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<CopyProfile>true</CopyProfile>
</component>
</settings>
<cpi

fflineImage cpi:source="wim:c:/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

superlulu · 01 Feb 2017

So, I try an other thing.
I flash one pc with an image without sysprep. I've installed Excel 2010 in audit mode and it works fine. Then I enter to oobe mode, without generalize and with my xml file, all is ok. But, if I generalize, the issue appears...

Kari · 01 Feb 2017

I really do not know why that happens. Myself currently using Office 2016 without an issue, all machines deployed using a heavily customized, sysprepped and generalized deployment image, even user profiles relocated on another drive. Office has no issues.

Microsoft TechNet has a support article about deploying Office 2010: Configure Office 2010 for capturing an image

If that article does not help, you should contact Microsoft Support to get help.

superlulu · 01 Feb 2017

I found a solution !

I don't know why but i need to replace folder c:\users\profilname\appdata\roaming\microsoft\office by the folder c:\users\administrator\appdata\roaming\microsoft\office .
Then it works fine...