I'm using the deployuserstates and scanuserstatesoffline script with windows shares. I've got the scanning script working but I'm having issues with the deploy script. I don't have the user's .mig files being saved to a system drive and I'm having problems getting it to point to where I have saved the user states. Anybody have any suggestions or know of a modified version of the script that came with k2000 is that works with network shares?
1 Comment   [ + ] Show Comment

Comments

  • wmashbrn and I are doing is our images are stored on our file server following this KB http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wims-k2000-version-3-6. So what we need to know is, is anyone else using the profile copy while their images are stored on a file server. If so how are you getting the deploy script to work?

    The capture script is placing the profiles on the T drive. But it's placing them on the root of T and every time it scans it's creating folder random folder names like this 3923793588_1414724951464
    and then in the folder if the capture goes through the profiles are in their own folders labeled by their SID's.
Please log in to comment

Answers

0
Any deployment system using a local service account for deployment is not going to have access to the network as LocalSystem is not validated for network access.  You would need to connect to a network share using a domain account in order to be able to access network content. Or you could set up a null session share on a server if you understand that this is a total security bust.
Answered 11/06/2014 by: EdT
Red Belt

  • wmashbrn and I are doing is our images are stored on our file server following this KB http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wims-k2000-version-3-6. So what we need to know is, is anyone else using the profile copy while their images are stored on a file server. If so how are you getting the deploy script to work? The capture script is placing the profiles on the T drive. But it's placing them on the root of T and every time it scans it's creating folder random folder names like this 3923793588_1414724951464 and then in the folder if the capture goes through the profiles are in their own folders labeled by their SID's.
Please log in to comment
Answer this question or Comment on this question for clarity