OME failing to remotely install Server Administrator

I've checked the NTFS permissions on the SystemUpdate folder, and Local Admins have Full Control over the folder and its children (I'm a domain admin which are local admins.)

I can browse to the admin$ share on the target successfully from the OME server using my credentials.  

Could you please clarify 'network discovery on the target' ?

I had enabled network discovery on the OME server, but just checked and saw that it was OFF.  Following the directions here:  

social.technet.microsoft.com/.../e1cc2310-b4f7-4de5-818a-352d8f792de5

I was able to get network discovery to stay on.  FYI, the firewall is turned off on OME.

I do not have network discovery turned on for the target server.  It is running Windows Server 2003 R2 SP2; firewall is also turned off.

Yet, the files are still not created in the SystemUpdate folder on the OME server.

technet.microsoft.com/.../cc753176%28WS.10%29.aspx  -  enabling network discovery.  

Thank you very much for all of your help and time, Victor.

I put full control to the Users group and anything else I could to the SystemUpdate folder and push those permissions down to its children.

I deleted the previous task and recreated it.  I executed the task and verified the SysMgmt_6_5_0.msi was created under the Packages folder in SystemUpdate.  

I can see the msiexec kicked off on my target server where I want Server Administrator installed, but now the task is at a standstill.  Currently it is still at 0% and no activity on the processor for the target server.  

I wonder if you restart the DSM Essentials Task service if that would help.

if the files are not created on the SystemUpdate then the issue is on the essentials server.  

be sure when it fails that you are remaking the task from scratch.  also try to change the source of the msi.  

also try to give everyone full control of the systemupdate folder  then remake the task.  

thanks, and just to confirm: you did a "restart" on the Task Mgr service just to be sure?

Now that the files are copied and the Msiexec is running on the target now we need to troubleshoot the silent install on the target server.  

if you point the server administrator task at the setup.exe or the downloaded managed node self extracting zip you can experience this type of issue.  

No, I didn't do that.  I did reboot though! ; )  

Hi, here is another suggestion to consider:

Please check the Task manager service is running. Then go to the following folder “C:\$support$\OpenManage\windows\SystemsManagement\SysMgmt.msi” check the permissions. If the folder permissions are not fully accessible change them to be fully accessible or copy the content of the folder to a root location C:\

Then try again.

thanks,

Rob

Task Manager service is running on OME and the Sysmgmt.msi file has full permissions for everyone.  

I deleted and recreated the task with the same results.

I have the task pointed directly at the MSI file with the /qn switch.  I still receive the same error message from the start.

Well, I think we've collected what data we could here in the forum.  I'm at a loss.  It seems like it is deploying it out to the managed node ok.  I'll need to ask you to call 800-945-3355  to open a ticket with support.  From there, we can collect more info on your system, collect logs, etc., and hopefully get to a quick resolution.

Thanks,

Rob

Rob, Victor.  I don't know what the deal was, but the deployment kicked off.  I rebooted the test server and the OME server, set different creds so I can determine what processes were kicking off for the installation, and it all worked.  Thanks for giving me some valuable troubleshooting tips that I can document for me team!