Does the account you're using to map the i: drive have write access to that share? I've done something similar in the past, although I think how I did it was to save the profile to a local folder and then use a copy file action to move it to the profile repository - seemed to be quicker that way.
I can able to capture the profile and save it locally using USMT4.01. Here the thing is now I want to save the captured profile directly into Network shared path in the name of machine name. can you please help me how to get this?
scanstate.exe /i:MigUser.xml /i:MigApp.xml /i:MigDocs.xml C:\test /o /c /nocompress /Hardlink
If I give captured profile save path as network shared path instead of C:\test in above mentioned command its not saving. even before executing that above mentioned command we have mapped the network shard path to one drive letter and we were using that driver letter in the command like
scanstate.exe /i:MigUser.xml /i:MigApp.xml /i:MigDocs.xml W:\test /o /c /nocompress /Hardlink
Can you help me in this
I think in the past all I did was use a create foldoer action to create a folder in the network location where you are storing profiles and using %ldHostname% (or equivilent provisioning variable) as the folder name. Then copy the stored profile from the temp local folder to the network location. I'm not sure why but I seem to remember there being a reason that I didn't save directly to the network - perhaps it was just taking too long!
Here is the example and disadvantage for locally saving the captured profile
User Hard disk space=80GB
All users profiles size is =70GB
Now the free space in Hardisk is only 10 GB
tell me now How can I save the captured 70GB size profile in to temp folder which is in local drive which I have only 10gb free space, Thats why we are trying directly save the captured profile into network shard path.
Very often if I run the scanstate.exe from any domain user. it's capturing that particular domain user profile only and save it in local drive whereelse its not capturing the entire profiles whatever available inside of Documents and settings. why its doing like? can you help me in this regards also.
Scanstate.exe /i:MigUser.xml /i:MigApp.xml /i:MigDocs.xml C:\Test /o /c /nocompress /Hardlink
I was executing the above mentioned command line from one of the domain user,often its not capturing all the profiles its capturing the particular profile where we are executing the scanstate.exe. if I run the same command line from local administrator account, its capturing each and every profiles and save it in local drive folder.
Can you please help us in this...