In R1.5 you also need to give spesific rights to the windows user.
I don't remember the exact rights , but you need Prossess as a object token (or somethinge like that) and act as a part of the operating system.
It's described in the dokumentation, so it should be possible to find it.
Scheduler not working (LOGON NOT DEFINED)
-
RuSt
In ver. 1.5 you have to do some extra configuration.
Like this :
Configuring the server for export scheduling
Export scheduling requires prior configuration of the OmniVista 4760 server. You also need the following information:
• The logon and the password of the local server administrator - OsAdmin.
• The logon and the password of the OmniVista 4760 administrator - OmniAdmin.
• The logon (OsUser) and password (OsPassword ) of a domain network user.
Procedure:
1. Log on to the PC server as OsAdmin, then select Start > Programs > Administration tools > User manager.
2. Select Local strategy > Assign user rights. A window is displayed. Select the option Display advanced user rights.
3. Give the OsUser the following rights by positioning your cursor on the corresponding fields and by opening the Security menu:
o To operate as a part of the operating system.
o To increase the quotas.
o To replace a process level token.
o Open a local session.
4. Run the OmniVista 4760 client and connect as OmniAdmin.
5. Launch the Directory application, then click the System tab.
6. Browse the tree until you reach the following: Nmc > ServerName > Servers > ServerName> ExecdEx, then click the bottom tab NT account.
7. Complete the fields:
o User: [Dom_Work]\OsUser.
Note: For an NT domain: Dom_Work is equivalent to domain name. For a Workgroup: Dom_Work is equivalent to the name Host 4760.
o Password: OsPassword.
I have attached this as an word-doc, if it's hard to read this.
I hope this will fix your proublems.
Like this :
Configuring the server for export scheduling
Export scheduling requires prior configuration of the OmniVista 4760 server. You also need the following information:
• The logon and the password of the local server administrator - OsAdmin.
• The logon and the password of the OmniVista 4760 administrator - OmniAdmin.
• The logon (OsUser) and password (OsPassword ) of a domain network user.
Procedure:
1. Log on to the PC server as OsAdmin, then select Start > Programs > Administration tools > User manager.
2. Select Local strategy > Assign user rights. A window is displayed. Select the option Display advanced user rights.
3. Give the OsUser the following rights by positioning your cursor on the corresponding fields and by opening the Security menu:
o To operate as a part of the operating system.
o To increase the quotas.
o To replace a process level token.
o Open a local session.
4. Run the OmniVista 4760 client and connect as OmniAdmin.
5. Launch the Directory application, then click the System tab.
6. Browse the tree until you reach the following: Nmc > ServerName > Servers > ServerName> ExecdEx, then click the bottom tab NT account.
7. Complete the fields:
o User: [Dom_Work]\OsUser.
Note: For an NT domain: Dom_Work is equivalent to domain name. For a Workgroup: Dom_Work is equivalent to the name Host 4760.
o Password: OsPassword.
I have attached this as an word-doc, if it's hard to read this.
I hope this will fix your proublems.
-
harogie1
Export via email
Hi you all
Please I have been priviledged to go through a formal training on 4760 configuration. However, through self training from a colleague who went for the training in France, I can try. Right now I face an export via email problem. The documentation seems not to be f=detailed enough. Please can someone assist in listing the detailed/comprehensive steps I need to take to set this up?
A client is already on me!
Thanks and regards.
harogie1
Please I have been priviledged to go through a formal training on 4760 configuration. However, through self training from a colleague who went for the training in France, I can try. Right now I face an export via email problem. The documentation seems not to be f=detailed enough. Please can someone assist in listing the detailed/comprehensive steps I need to take to set this up?
A client is already on me!
Thanks and regards.
harogie1
-
knightr1der
Re: Scheduler not working (LOGON NOT DEFINED)
There really isn't too much to do for emailing reports...unless I am mistaken, in which case one of my friends on here will correct me.
You need to make sure of 2 things first;
1. The Server is a registered member in the local domain.
2. The mail server is defined in the 4760 server - you can check this in /directory/servers (I'm not sure exactly the location without looking at a 4760 server.
If the above is OK, then you can just choose to export the report to a email address. Th eoptions to export are; Export to txt file, Export to Excel File, Export to Web style file, Export to PDF file or email
You need to make sure of 2 things first;
1. The Server is a registered member in the local domain.
2. The mail server is defined in the 4760 server - you can check this in /directory/servers (I'm not sure exactly the location without looking at a 4760 server.
If the above is OK, then you can just choose to export the report to a email address. Th eoptions to export are; Export to txt file, Export to Excel File, Export to Web style file, Export to PDF file or email
