@elwayfan446 Good to know. My organization has also changed the server policy to let the user_id and password to be stored. I just provided the answer for someone who had the same problem, if the server policy did not allow to store the credentials in the desktop. ... View more

@ChrisHemedinger I found it did not need the credentials.xml in EG7.1 to schedule a project. I tested and it worked without setting up this credentials.xml. The only problem was the sever policy had overwriten the contents in the configurationV71.xml. If set to read only, then your user_id , password would always be there.  From the link you provided, (http://support.sas.com/kb/30/917.html)   "If logon credentials for the SAS Metadata Server are not cached on the client side, scheduling of SAS Enterprise Guide projects is not possible."   To edit the configurationV71.xml by adding user_id, password and active profile name and set this file to read only will cache the logon credentials on the client side and allow the project to be scheduled.  ... View more

In the folder C:\users\myvunetid\appdata\roaming\sas\metadataserverprofiles (myvunetid is my vunet-id) there is a file named “configurationV71.xml” Change the contents to  as follows: <?xml version="1.0" encoding="utf-8"?> <Configuration LastWrittenBy="Engine Configuration Manager" FileVersion="2">   <Profiles>     <Profile>       <Name>******</Name>       <Description>******</Description>       <Type>OMS</Type>       <Hosts>         <Host machine="*****" port="8561" />       </Hosts>       <UseIWA>False</UseIWA>       <SaveLogin>True</SaveLogin>       <User>******</User>       <Password>****** </Password>       <DefaultServer>SASApp</DefaultServer>     </Profile>   </Profiles>   <Settings>     <ActiveProfile>******</ActiveProfile>     <GenerateLocalServer>False</GenerateLocalServer>   </Settings> </Configuration>   Change ****** to real names you would use. Please use proc pwencode in='your-password'; run; to generate encode password like: {sas002}6FE4B62647E0E59721B8CAD44A12345C Put the encode word as the password in the xml file. The most important part is you must set this file (configurationV7.xml)  to read only. This will prevent the globe policy to update it (which would set user_id and password to space and ask you to key in).   This method stored the user_id, password and the active profile name in your local desktop. It would not be changed by your domain policy. You can schedule the project (you must put the active profile name in the configurationV71.xml to let EG directly link to that profile).   This may be the only way I can find to schedule the EG project on your desktop if the domain policy would ask your credentials every time when you open the EG.  ... View more