FruitGuy Posted September 14, 2015 Report post Posted September 14, 2015 So I've noticed that when I image a machine, it seems to take about 30+ minutes before I can remote to it. As soon as OSD is done and it goes to the Ctrl+Alt+Del screen, I can remote to it. But then I have the user reboot and I can't link to it for about 30+ minutes. I have the user reboot, because I've noticed for some reason, I can't access any network shares until I do. Any idea on what I can do to fix this? Quote Share this post Link to post Share on other sites More sharing options...
FruitGuy Posted September 14, 2015 Report post Posted September 14, 2015 Also, I'm referring to Remote Control, not Remote Assistance or anything like that. Quote Share this post Link to post Share on other sites More sharing options...
phil_w Posted September 14, 2015 Report post Posted September 14, 2015 Is the client actually working at that point? It could be it's taking a while to come out of provisioning mode for some reason, if you haven't already you may want to add a step at the end of your task sequence to change the registry keys to bring the client out of provisioning mode. Since you're finding you have to restart for your network drives to work, have you tried adding an additional restart step at the end of your task sequence? Quote Share this post Link to post Share on other sites More sharing options...
FruitGuy Posted September 15, 2015 Report post Posted September 15, 2015 what registry keys need to be changed? I'm new to the whole OSD thru SCCM, we just implemented it. I'd been using MDT for imaging and LanDesk for Remote Control. Quote Share this post Link to post Share on other sites More sharing options...
FruitGuy Posted September 15, 2015 Report post Posted September 15, 2015 Alright so I googled that. That isn't the issue. The registry key for provisioning is set to false when I login, and again after I login after reboot. Quote Share this post Link to post Share on other sites More sharing options...
Jaybone Posted September 15, 2015 Report post Posted September 15, 2015 Updates, maybe? Depending on how things are set up, you may be in a situation where the client's installed at a lower patch level, detecting that, then running updates on itself. Quote Share this post Link to post Share on other sites More sharing options...
FruitGuy Posted September 15, 2015 Report post Posted September 15, 2015 Alright, I found the issue. The Default Client settings were not something that I got to configure on the front end. I started poking my head around there and saw that the default settings had Remote Tools disabled. Which is why, once it pulled in the actual policy, everything at a later time worked like it should. Sorry for wasting everyone's time, I had assumed something like this would have been setup correctly to begin with. Quote Share this post Link to post Share on other sites More sharing options...
