KNOWN ISSUE: Dagent won''t connect to DS if it''s unable to delete Setupcomplete.cmd at start up

Article:TECH127634  |  Created: 2010-05-25  |  Updated: 2010-05-25  |  Article URL http://www.symantec.com/docs/TECH127634
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



Dagent doesn't communicate with its Deployment Server because it's unable to delete the file Setupcomplete.cmd from the C:\Windows\Setup\Scripts\ folder.


Environment



DS 6.9 sp4

Agent installed on a Server 2008 R2 x64

Usually occurs after a scripted OS install on a Dell Server or after a recovery CD has been ran on a Dell server to reinstall the OS.

Dell Servers

Cause



The Setupcomplete.cmd file is in use or is marked at read only which prevent it from being deleted.  Dagent needs to delete this file as part of its start to be able to communicate to DS.

This is a known issue that has been sent to development for review.


Solution



Currently there isn't a fix for this.  Development is reviewing the issue at this time.

As a work around you can remove the read only attribute or wait until the file is no longer in use and then restart the Dagent service and it should then be able to communicate to its DS.


Supplemental Materials

SourceDEFECT
ValueETK 2054776
DescriptionLogged in Etrack (Symantec) database

Legacy ID



53053


Article URL http://www.symantec.com/docs/TECH127634


Terms of use for this information are found in Legal Notices