
|
Manage Email Signatures Centrally - For All Users extend your brand and promote your products, services, special events and news
|
| View previous topic :: View next topic |
| Author |
Message |
mrcomputerman Just popping in
Joined: 19 Mar 2008 Posts: 2
|
| Posted: Thu Mar 20, 2008 9:48 pm Post subject: Non Domain Joined Workstations In An AD Environment |
|
|
Good Day,
We have several notebooks / laptops in use by our mobile workforce. Our deployment to domain-joined workstations was very straightforward but we are unable to use this solution on our mobile workstations.
Steps We've Taken
We have verified that the permissions are set on the folder containing settings.mdb to allow access from any of our workstations. We can successfully browse and manipulate files in this location.
We have created a simple batch file named sign.bat and put it in the same location as the settings.mdb file and we are able to successfully execute the batch file. We used this same batch file to successfully connect from our domain joined workstations. Please see our code below:
| Code: |
Start \\myserver0001\emailsignature\sign.exe Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\myserver0001\emailsignature\settings.mdb
|
When we execute this same batch file from our mobile non-domain joined workstations, we see the following in the Cockpit,
"You are not logged into a domain (3001B). -Signatures from default settings, no group settings or individual settings apply."
In researching your forum, we came across a post Reading AD for non Domain Clients here: http://www.emailsignature.eu/phpBB2/reading-ad-for-non-domain-clients-t771.html
However, this "root" data string already existed on the server and when merged with the workstations registry we still were not successfully adding the signatures in Outlook. After the change to the registry and running the aforementioned sign.bat, we see the following in the Cockpit,
"The root=LDAP://DC=stark,DC=mrcomputerman,DC=local cannot be contacted. Please make sure it is correct (3001A)." And are still unable to send messages using the appropriate signature.
I am curious to know how our non-domain clients would know which AD user to pull data for (in the signature) without A. being joined to the domain OR B. passing domain credentials at some point.
Your assistance is appreciated.
Thank you
Paul Luckett |
|
| Back to top |
|
 |
Jesper Frier Certified Professional


Joined: 09 Sep 2006 Posts: 1940 Location: Stoevring, Denmark
|
| Posted: Fri Mar 21, 2008 7:21 am Post subject: |
|
|
As I read your post, you have signatures setup using Active Directory data source - and you want to deploy those signatures to remote users which are not part of your Active Directory.
If that is the case, you need to create new signatures for your remote users that uses a data source they have access to.
I may have misunderstood ...  |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|