| T O P I C R E V I E W |
| joshyz73 |
Posted - 05/03/2012 : 3:39:16 PM
We just upgraded to MDT2012 from MDT2012 Beta. After the upgrade, something odd is happening with the capture user state options. I have UserDataLocation=NETWORK, and a UDShare and UDDir set in my customsettings.ini. In both the beta and MDT2010, the User Data screen in the Lite Touch Wizard (the one that says "Specify where to save your data and settings") would have "Automatically determine the location" selected, with the "Allow data and settings to be stored locally when possible" box unchecked (we don't want hard-linking). Now, when that screen comes up, it has "Specify a location" selected, with the "Location:" box empty. If I select auto, then continue through, the process uses hard-linking (even though I don't check the box that would allow it).
No changes were made in my UDDir or UDShare parameters, and the UDShare path exists and is connectable. The weird thing is, on the next screen (computer backup), the "Specify a location" option is selected and is populated (I have ComputerBackupLocation, BackupShare, and BackupDir set in cs.ini). Has anyone else noticed this, and if so, how can it be fixed? |
| 10 L A T E S T R E P L I E S (Newest First) |
| ervi |
Posted - 09/18/2012 : 07:41:29 AM
If you want to automate userdata backup to a share. Add these properties to your cs.ini
- SkipUserData=Yes
- UserDataLocation=Network
- UDShare=\\yourserver\yourshare
- UDDIR=%Computername%
Above propertis will automate the whole userdata backup process. Also if you use ODSComputername for UDDIR it will not use actual computername of workstation backedup but computername specified by OSDComputername property in CS.ini
If you just want to pre fill userdata window use these properties in CS.ini
- SkipUserData=NO
- UserDataLocation=Network
- UserDataLocation=\\yourserver\yourshare\%computername%
|
| CypherBit |
Posted - 09/06/2012 : 1:20:19 PM
I have the exact same issue as joshyz73.
I don't want to set it to Yes/skip it, since there are times where a backup isn't required and I'd like to keep that option.
joshyz73 have you resolved your issue and how?
|
| drewlt |
Posted - 06/23/2012 : 3:32:08 PM
I'm seeing a similar thing - Prompting for "Specify a location" with an empty location.
UserDataLocation=NETWORK
UDShare=\\server\usmtdata
UDDir=%OSDComputerName%
Setting SkipUserData=YES seemed to take the data - bug in the wizard hta page not grabbing the Customsettings.ini?
edit: yep, editing DeployWiz_UserData.vbs after line 34:
DataPath.value = property("UDShare") + "\" + property("UDDir")
Works well but doesn't swap out the actual computer name property.
I ended up just skipping the wizard page as I didn't want to build the code to swap out %OSDComputerName% property (or others in the config).
-Andrew |
| arwidmark |
Posted - 05/07/2012 : 3:38:15 PM
If you specify the UserDataLocation=NETWORK and the UDSHARE and UDDIR values you should also hide that wizard pane. The MDT 2012 deployment wizard doesn't correcly use the values you specficy in the rules for the User Data pane. This might be a known issue, I will check with the team...
That being said, I did some testing with a new MDT 2012 deployment share, refreshing a Windows XP workstations to Windows 7. If I set UserDataLocation=NETWORK and the UDSHARE and UDDIR values it does indeed store my data on the server, no hard linking on the client. And it will do the same even if I'm displaying the User Data pane (SkipUserData=NO) and type in the path manually.
Shorthand, I can't reproduce what you are seeing with MDT 2012 using hardlinks even when UserDataLocation=NETWORK and the UDSHARE and UDDIR values are set.
Can you please send me all your logfiles? email to my last name, and I'm using gmail...
/ Johan |
| joshyz73 |
Posted - 05/07/2012 : 07:24:57 AM
quote:
Originally posted by Archee
Is %ComputerName% still working in MDT2012?
Should be obsolete in MDT2010 for benefit of %OSDComputerName%.
I've tried both. I have been using %ComputerName% since MDT2010, and it still works if it's used as the "BackupDir" parameter. Again, everything was working as it had under MDT2010 all the way through MDT2012 BETA 2. It broke in the MDT2012 full release. |
| Archee |
Posted - 05/07/2012 : 07:07:03 AM
Is %ComputerName% still working in MDT2012?
Should be obsolete in MDT2010 for benefit of %OSDComputerName%. |
| joshyz73 |
Posted - 05/04/2012 : 2:46:18 PM
quote:
Originally posted by arwidmark
Sounds like a bug then, I always use hardlinking so I haven't seen it before... Can you post your customsettings.ini? or mail it to me? my email alias is my last name and I'm using gmail...
/ Johan
Here's what I'm using currently:
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipBDDWelcome=YES
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
ScanStateArgs=/ue:*\* /ui:DOMAINNAME\* /c
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
USMTMigFiles003=MigDocs.xml
USMTConfigFile=CustomConfigFile.xml
SkipLocaleSelection=YES
SkipComputerBackup=NO
KeyboardLocale=en-us
UserLocale=en-us
InputLocale=0409:00000409
UILanguage=en-US
SkipTimeZone=YES
TimeZoneName=Eastern Standard Time
MandatoryApplications001={250b261a-bc24-43ac-88f8-efabd6cddbe8}
ComputerBackupLocation=NETWORK
BackupShare=\\NAS_SERVER\MDTFULLBACKUP
BackupDir=%ComputerName%
UserDataLocation=NETWORK
UDShare=\\NAS_SERVER\MDTUSMT
UDDir=%ComputerName%
SkipFinalSummary=YES
FinishAction=LOGOFF
I generalized the server names and domain, but that's it. If you need to see the original, I can email it. |
| arwidmark |
Posted - 05/04/2012 : 2:27:10 PM
Sounds like a bug then, I always use hardlinking so I haven't seen it before... Can you post your customsettings.ini? or mail it to me? my email alias is my last name and I'm using gmail...
/ Johan |
| joshyz73 |
Posted - 05/04/2012 : 1:16:20 PM
Thanks for that info. I was suspecting that might have been a cause of the issue. However, I just did a completely fresh install of MDT and created a new deployment share. I didn't use any of my files from the existing one (other than the OS .wim file), and get the exact same behavior. |
| arwidmark |
Posted - 05/04/2012 : 12:07:45 AM
First, upgrades from Beta is not supported and may cause all sorts of problem... Create a new deployment share, or restore your old MDT 2010 Update 1 share and upgrade that one.
If the problem still exist after creating a new deployment share in MDT 2012 RTM, please post back and I will help you investigate.
/ Johan |
