Hmmm, I never thought about it, but it's not surprising. From what we've been 
told, the only significant thing is the DB and the site restore process only 
uses the DB regardless of how the DB was backed up. Thus, even if you are using 
the built-in backup maintenance task, only the DB is used and the rest is 
ignored. Given that the configuration.mof file is not in the DB, it's ignored 
and the default is rebuilt, re-extracted, or something similar.

J

From: [email protected] [mailto:[email protected]] On 
Behalf Of Spinelli, Robert J
Sent: Friday, September 6, 2013 12:58 PM
To: [email protected]
Subject: [mssms] Restore doesn't restore configuration.mof - SCCM 2012 SP1

I was doing some work in the lab and performing a restore and was surprised to 
see that our custom configuration.mof that was backed up wasn't actually 
restored.  The restore process put back the default configuration.mof

Can anyone else confirm they had to drop their custom configuration.mof back 
into inboxes\clifiles.src\hinv after performing a restore.

Thank you.

Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, 
United States| T: +1.201.595.6820 | C: +1.917.538.6192 | 
[email protected]<mailto:[email protected]>


This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All market prices, data and 
other information are not warranted as to completeness or accuracy and are 
subject to change without notice. Any comments or statements made herein do not 
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and 
affiliates. This transmission may contain information that is proprietary, 
privileged, confidential and/or exempt from disclosure under applicable law. If 
you are not the intended recipient, you are hereby notified that any 
disclosure, copying, distribution, or use of the information contained herein 
(including any reliance thereon) is STRICTLY PROHIBITED. Although this 
transmission and any attachments are believed to be free of any virus or other 
defect that might affect any computer system into which it is received and 
opened, it is the responsibility of the recipient to ensure that it is virus 
free and no responsibility is accepted by JPMorgan Chase & Co., its 
subsidiaries and affiliates, as applicable, for any loss or damage arising in 
any way from its use. If you received this transmission in error, please 
immediately contact the sender and destroy the material in its entirety, 
whether in electronic or hard copy format. Thank you. Please refer to 
http://www.jpmorgan.com/pages/disclosures for disclosures relating to European 
legal entities.




Reply via email to