Hello, I am wondering if anyone has successfully deployed Teamcenter 8.3 with SCCM 2012?
It continues to fail for some reason, while the same script will install fine if I run it manually. The log file is not much help, only listing this:
Copying file N:\Applications\Teamcenter\Media\Installation\tc8.
Installation interrupted due the following reason:
Time: Wed Jun 11 10:16:06 EDT 2014
Copying file d:\plmapps\TC83\install\configuration.xml to d:\plmapps\TC83\install\configuration1406111016.xm
Is there a way to determine which registry key is being queried and not found? And why running this as the System account (Which sccm uses) causes it to fail, while running as an other account makes it work?
If anyone has any input, that would be most helpful.
We are using SCCM 2012 to deploy it. It isn't pretty though and fails a lot even though SCCM thinks it was successful.
When we were troubleshooting, we found that it was looking for the following registry key.
Windows Registry Editor Version 5.00 [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\Cu
rrentVersion\Explorer\Shell Folders] "Desktop"=hex(2):63,00,3a,00,5c,00,74,00,65,00,6d, 00,70,00,5c,00,64,00,65,00,\ 73,00,6b,00,74,00,6f,00,70,00,00,00 "Programs"=hex(2):63,00,3a,00,5c,00,74,00,65,00,6d ,00,70,00,5c,00,70,00,72,00,\ 6f,00,67,00,72,00,61,00,6d,00,73,00,00,00
During the installation, we import that registry key and at the end we over-write it with the default.
We also use batch files for the installation. Siemens wasn't much help on this either.
If you find a better way, I would be very interested in hearing it.
Hope this helps.
SCCM runs under the Local System account which can have problems with virtual folders like "Desktop". Build and maintain your images using Microsoft Deployment Toolkit (MDT) 2010 then distribute the images using SCCM. Here's a super article
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3