creating driver share on k2000 RSAs?
Probably a very easy question to answer, but i want to use a drivers_post install folder and sync my drivers using the driver work around. How do I create the folder? there doesn't appear to be a way to create the folder. I can't access the box through windows explorer at all and it never prompts me for authentication if I just put \\ekbox\ there.
I feel like I've missed something simple but I can't find what, as the interface for the extender is quite basic.
Would love to get rid of the attached error.
I feel like I've missed something simple but I can't find what, as the interface for the extender is quite basic.
Would love to get rid of the attached error.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
dchristian
13 years ago
It looks like the workaround is happening before windows gets installed.
Did you setup the copy driver feed as a pre or post install task?
It should be set as a post-install task that runs in the boot environment.
When you see it in the list of available tasks, it should be in the second section in green.
Did you setup the copy driver feed as a pre or post install task?
It should be set as a post-install task that runs in the boot environment.
When you see it in the list of available tasks, it should be in the second section in green.
Posted by:
dchristian
13 years ago
Sorry just read the previous post fully...
The drivers_postinstall folder get created after you upload the drive feed bin.
[link]http://www.kace.com/support/kb/index.php?action=artikel&cat=59&id=1103&artlang=en[/link]
The drivers_postinstall folder get created after you upload the drive feed bin.
[link]http://www.kace.com/support/kb/index.php?action=artikel&cat=59&id=1103&artlang=en[/link]
Posted by:
dogfish182
13 years ago
sorry I should note that my k2000 works perfectly, we are using the driver feed and workaround and it's working great at our main office.
Next step is to install an RSA at our remote location. I did that and linked the appliance, that's working fine as well, also dhcp sends the traffic to the RSA for pxe deployment. Everything great, however once it comes to using the build for our machines that works perfectly from our main office, it fails out at the above step. This is because it's looking on the RSA for drivers_postinstall. Which doesn't exist. During sync from the K2000 to the RSA it doesn't appear to create these. I can't create them manually either, as there isn't any kind of default file share I can activate as far as I can tell?
Next step is to install an RSA at our remote location. I did that and linked the appliance, that's working fine as well, also dhcp sends the traffic to the RSA for pxe deployment. Everything great, however once it comes to using the build for our machines that works perfectly from our main office, it fails out at the above step. This is because it's looking on the RSA for drivers_postinstall. Which doesn't exist. During sync from the K2000 to the RSA it doesn't appear to create these. I can't create them manually either, as there isn't any kind of default file share I can activate as far as I can tell?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.