Re: Zenworks 7 Linux Management Device Registration Issue

On Tue, 08 Nov 2005 02:35:13 GMT, [email protected] wrote:
> All,
>
> Below is a detailed description of a resistration issue using Zenworks
> Linux Management 7.
duplicate question - can I gently mention a point? Whilst we naturally
understand that you may need information/help in a hurry, asking the
same question in multiple forums dilutes the answers you get, and makes
more work for those of us who have to read them; it would help if you
could avoid this in future.
Many thanks
(c) Shaun Pond, stolen without permission ;-)
Marcus Breiden
Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

On Tue, 08 Nov 2005 02:39:10 GMT, [email protected] wrote:
> Below is a detailed description of a resistration issue using Zenworks
> Linux Management 7
duplicate question - can I gently mention a point? Whilst we naturally
understand that you may need information/help in a hurry, asking the
same question in multiple forums dilutes the answers you get, and makes
more work for those of us who have to read them; it would help if you
could avoid this in future.
Many thanks
(c) Shaun Pond, stolen without permission ;-)
Marcus Breiden
Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

Similar Messages

Zenworks Linux Management Device Registration Issue

All,
Below is a detailed description of a resistration issue using Zenworks
Linux Management 7.
Hardware Configuration:
1- DSL Modem (Westell Model 2200)
1- DI 614+ 2.4 GHz Broadband Wireless Router (includes 4-5 ethernet
ports) with a IP address of 192.168.0.1
1- PC Server running Redhat SUSE Linux Enterprise Server 9 (has a static
IP address of 192.168.0.103). This machine is running the Zenworks 7
Linux Management Software and is able to sucessfully launch the Zenworks
7 Control Panel.
1- Redhat Linux Enterprise Server 3 on a completely different network
with a static IP address (207.44.142.56). This machine is running the
Zenworks Linux Management Agent install using the ./zlm-install -a
command.
Network Configuration:
The broadband DSL modem is connected directly to the WAN ethernet port on
the wireless router
The primary PC server running Redhat SUSE Linux Enterprise Server 9 has a
direct connection to one of the ethernet ports on the wireless broadboard
router with a private static IP address of 192.168.0.103 and has a public
IP of 70.22.107.168.
The DSL modem is has a direct connection to the telephone line.
The Redhat Linux Enterprise Server 3 is on a completely different network
with a IP of 207.44.142.56.
No firewalls are configured on the primary server and the wireless router
Port Forwarders are configured on the broadband wireless router as
follows:
zlm1
192.168.0.103
TCP 80/80
always
zlm2
192.168.0.103
TCP 443/443
always
zlm3
192.168.0.103
TCP 524/524
always
zlm4
192.168.0.103
TCP 1299/1299
always
zlm5
192.168.0.103
TCP 2544/2544
always
zlm6
192.168.0.103
TCP 5506/5506
always
zlm7
192.168.0.103
TCP 10389/10389
always
zlm8
192.168.0.103
TCP 10636/10636
always
Goal:
To successfully register the Redhat Linux Enterprise 3 server (i.e. the
managed device with IP 207.44.142.56) with the primary server
(192.168.0.103 SUSE Redhat Enterprise Server 9 machine) so it can be
viewed and managed from the Zenworks 7 Control panel.
Nature of Problem:
When attempting to register the managed device (207.44.142.56) with the
primary server (192.168.0.103) which resides inside of my Wireless Local
Area Network (WLAN) via the following command, it appears to fail. I'm
unable to view or configure this managed device inside of the Zenworks 7
Linux Management Control Panel. The following are 2 manual approaches
that I take to register the managed device and the results for each.
Register using private IP approach:
/opt/novell/zenworks/bin/rug sa https://192.168.0.103
Results: ERROR: Could not add 'https://192.168.0.103': Download failed:
(https://192.168.0.103/zenworks-registration/service.xml) Error:
ConnectFailure
Register using public IP approach:
/opt/novell/zenworks/bin/rug sa https://70.22.107.168
Results: ERROR: Could not add 'https://70.22.107.168': Download failed:
(https://70.22.107.168/zenworks-registration/service.xml) Error:
ConnectFailure
Regards,
Darrick Addison
Sr. Software Engineer/Consultant
ASC Technologies, LLC
Ph: 443.257.9116
Fax: 410.360.5570
E-mail: [email protected]
Web: www.asctllc.com

On Tue, 08 Nov 2005 02:40:58 GMT, [email protected] wrote:
> Below is a detailed description of a resistration issue using Zenworks
> Linux Management 7.
duplicate question - can I gently mention a point? Whilst we naturally
understand that you may need information/help in a hurry, asking the
same question in multiple forums dilutes the answers you get, and makes
more work for those of us who have to read them; it would help if you
could avoid this in future.
Many thanks
(c) Shaun Pond, stolen without permission ;-)
Marcus Breiden
Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

Zenworks 7 Linux Management Device Registration Issue

All,
Below is a detailed description of a resistration issue using Zenworks
Linux Management 7.
Hardware Configuration:
1- DSL Modem (Westell Model 2200)
1- DI 614+ 2.4 GHz Broadband Wireless Router (includes 4-5 ethernet
ports) with a IP address of 192.168.0.1
1- PC Server running Redhat SUSE Linux Enterprise Server 9 (has a static
IP address of 192.168.0.103). This machine is running the Zenworks 7
Linux Management Software and is able to sucessfully launch the Zenworks
7 Control Panel.
1- Redhat Linux Enterprise Server 3 on a completely different network
with a static IP address (207.44.142.56). This machine is running the
Zenworks Linux Management Agent install using the ./zlm-install -a
command.
Network Configuration:
The broadband DSL modem is connected directly to the WAN ethernet port on
the wireless router
The primary PC server running Redhat SUSE Linux Enterprise Server 9 has a
direct connection to one of the ethernet ports on the wireless broadboard
router with a private static IP address of 192.168.0.103 and has a public
IP of 70.22.107.168.
The DSL modem is has a direct connection to the telephone line.
The Redhat Linux Enterprise Server 3 is on a completely different network
with a IP of 207.44.142.56.
No firewalls are configured on the primary server and the wireless router
Port Forwarders are configured on the broadband wireless router as
follows:
zlm1
192.168.0.103
TCP 80/80
always
zlm2
192.168.0.103
TCP 443/443
always
zlm3
192.168.0.103
TCP 524/524
always
zlm4
192.168.0.103
TCP 1299/1299
always
zlm5
192.168.0.103
TCP 2544/2544
always
zlm6
192.168.0.103
TCP 5506/5506
always
zlm7
192.168.0.103
TCP 10389/10389
always
zlm8
192.168.0.103
TCP 10636/10636
always
Goal:
To successfully register the Redhat Linux Enterprise 3 server (i.e. the
managed device with IP 207.44.142.56) with the primary server
(192.168.0.103 SUSE Redhat Enterprise Server 9 machine) so it can be
viewed and managed from the Zenworks 7 Control panel.
Nature of Problem:
When attempting to register the managed device (207.44.142.56) with the
primary server (192.168.0.103) which resides inside of my Wireless Local
Area Network (WLAN) via the following command, it appears to fail. I'm
unable to view or configure this managed device inside of the Zenworks 7
Linux Management Control Panel. The following are 2 manual approaches
that I take to register the managed device and the results for each.
Register using private IP approach:
/opt/novell/zenworks/bin/rug sa https://192.168.0.103
Results: ERROR: Could not add 'https://192.168.0.103': Download failed:
(https://192.168.0.103/zenworks-registration/service.xml) Error:
ConnectFailure
Register using public IP approach:
/opt/novell/zenworks/bin/rug sa https://70.22.107.168
Results: ERROR: Could not add 'https://70.22.107.168': Download failed:
(https://70.22.107.168/zenworks-registration/service.xml) Error:
ConnectFailure
Regards,
Darrick Addison
Sr. Software Engineer/Consultant
ASC Technologies, LLC
Ph: 443.257.9116
Fax: 410.360.5570
E-mail: [email protected]
Web: www.asctllc.com

On Tue, 08 Nov 2005 02:37:16 GMT, [email protected] wrote:
> Below is a detailed description of a resistration issue using Zenworks
> Linux Management 7.
duplicate question - can I gently mention a point? Whilst we naturally
understand that you may need information/help in a hurry, asking the
same question in multiple forums dilutes the answers you get, and makes
more work for those of us who have to read them; it would help if you
could avoid this in future.
Many thanks
(c) Shaun Pond, stolen without permission ;-)
Marcus Breiden
Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

Zenworks Linux Management 7

I have installed the ZLM 7 Client on a NLD 9 computer. Since then I have
not been able to run the Red Carpet Update Manager nor have I been able
to run RPMS by clicking on them and it running in Red Carpet. I get a
Zenworks 7 Linux Management Update Manager login with Connect to this
system selected I click Connect. Once I do this the login window locks
and I am unable to get to the Management Window. Please Help! My ZLM 7
server is running on SUSE Enterprise server 9.

you'll get quicker answers I think if you ask this in the 7x forum
instead of 6x...
Shaun Pond

Hp system insight manager-device discover issue

Hi,
I have recently installed hp System Insight Manager 7.4. But I can't discover any hp device. The system did not respond to SNMP. when discover any hp device then System Insight Manager showing error:
Major: The system cannot be identified properly for HP SIM to manage;
              unable to get one or more of the following: model, serial number or
              unique identifier (UUID). For management processors, verify the
              system is running the latest firmware. For Linux based operating
              systems, you must have dmidecode installed, enable the
              PermitRootLogin and PasswordAuthentication in sshd, and use root
              sign-in credential. For HP-UX, verify the sign-in credential. For
              Windows, check if WMIMapper is configured correctly on the CMS and
              verify the sign-in credential.
Any ideas on a fix for this?
Thank you,
Nahid

I know there might be issues with cimserver and different versions of SMI-S solutions. SAN-OS 3.2 uses 1.1 and 3.3 and above uses 1.2. The changes are considerable and can make some SMI-S system not work well. I don't know if NX-OS is supported yet.
I don't use HP SIM so I really can't say for sure but its worth checking on what is supported.

Retail Execution Application Device Registration Issues

Hello Community,
I am having issues registering the Retail Execution application with a user in CRM.
I am testing with an iOS device where I downloaded the application from the app store and an Android device where I got the APK from the SAP marketplace.
The guide I am following is the Administrator's Guide SAP Retail Execution 3.2.0.
There are a few issues i've come across which I think might be contributing to my devices not enrolling.
I've completed the setup of the environment till the point in the documentation for Data Change Notification where I need to create an RFC connection to the SMP server.
I entered the IP address for the SUP server with the port as 80. Is port 80 correct?
The username ive setup as supAdmin@Admin with the password.
When I test the connection I get a : Status HTTP Response 404 error.
Another issue I have is that in the documentation under the section enrolling a device using the Relay Server, all the fields are referring to SMP username, SMP Farm ID, SMP Activation code and so on. The connection details I have used in other apps are as follows:
Server : <ip of relay server>
Farm : Relay server Farm ID
Username : jcommerford@crm (CRM login ID @ security configuration - crm is my HTTPAuthentication security configuration I created in SUP)
password :
Port : 80 (relay server port)
URL suffix : leave blank
Domain : The new domain I created in SUP and where the Rex MBO is deployed.
So it isnt making sense as to what details need to go into here.
Lastly...
What is the absolute minimum setup of the CRM system and SUP to register a user through the relay server?
I would like to comment that I havnt performed the initial download of Master Data using DCN but didnt think this was needed to enrol a device. Other than that the guide was followed and configuration done according to it.
Let me know if anymore information is needed as I am very stressed to get this issue sorted out.
Thank you
Jared

Hello Jared
Has the registration worked without the Relay server setup? I would suggest you try that first.
I am assuming you already set the SM59 destinations for CRM to SMP and trusted RFC to corresponding ECC (but this is not necessarily the issue, because the registration is failing).
Please confirm that the RFC Destination is set as follows (use the supAdmin user on the Logon & Security page)
Check the security provider on SMP (your's may be different but I am using the following for POC and it works)
Could you please confirm if the REX package was deployed correctly on the SMP server by selecting the connection pools for both CRM and ECC for corresponding MBO's
Please post a log of the SMP server once you switch to direct registration to SMP (without relay server)
Thanks
Raza.

X230 Win 8.1 Power Management Device Driver Issue

Hi,
Fresh Win 8 build, in place upgrade to 8.1. Then all Lenovo tools updated and latest Lenovo compatability package installed.
This device is not detected properly. I believe it is a Power Manager driver issue (based on an older post with the same problem, but no resolution posted).
Lenovo X230
Type: 2330-A59
Device instance path: ACPI\LEN0078\5&2890D699&0
Location: on Microsoft ACPI-Compliant Embedded Controller
I've tried the typical deletion of the device and re-run the PM driver install package (latest from Lenovo.com). No change. The device is listed back in Device Manager as an "Unknown" device.
Anyone out there know the solution? I hope it is something I am just over looking.
JIM
Solved!
Go to Solution.

Found the answer. It is NOT the PM Driver.
Lenovo HID HW Radio Driver for Windows 8.1 (32-bit , 64-bit), 8 (32-bit , 64-bit) - ThinkPad ... Learn more
Version
: 1.0.0.54
This resolved the issue! It's too bad the System Update tool did not capture this.
JIM

Configuring rcd to contact you Zenworks Linux Management server

I am new to Zenworks and am installing version 6.6. Under installing the
client on a single machine in step 6 it says to run the following command
rug service-add https://youZLMserver/data
If I use the above server I get the following message
ERROR: Unable to mount service for 'https://yourZLMserver/data': Unable to
download service info: IO error - Soup error: Cannot resolve hostname (2)
When I run this command i get the following message subsituting my server
address
ERROR: Unable to mount service for 'https://136.174.209.92/data': Unable to
down
Nowhere do I find a directory called /data or remember one being created.
Any help in getting past this point would be greatly apprecieated.
Kevin

I better try things before asking :) The problem is that the ssl cert ain't
trusted. you can turn it of with. Or trust the cert
rug set require-verified-certificates false
Johan Blom wrote:
> I have the same problem
>
> Anyone solved this?
>
>
> [email protected] wrote:
>
>
>
>> I am new to Zenworks and am installing version 6.6. Under installing the
>> client on a single machine in step 6 it says to run the following command
>>
>> rug service-add https://youZLMserver/data
>>
>> If I use the above server I get the following message
>>
>> ERROR: Unable to mount service for 'https://yourZLMserver/data': Unable
>> to download service info: IO error - Soup error: Cannot resolve hostname
>> (2)
>>
>> When I run this command i get the following message subsituting my server
>> address
>>
>> ERROR: Unable to mount service for 'https://136.174.209.92/data': Unable
>> to down
>>
>> Nowhere do I find a directory called /data or remember one being created.
>> Any help in getting past this point would be greatly apprecieated.
>>
>> Kevin

Re: Device Registration Issue

Hi I have problems with silverlight not working, I am not on private browsing, I have just reinstalled the latest version of silverlightand also checked that my apple mac is registered which is confirmed, not sure what to do next?

What error message are you seeing or what is happening, the more information you can post the better.

"drm device registration failed" Verizon Media Manager android tablet

I get the error "drm device registration failed" using Verizon Media Manager on an android tablet. Any ideas?

Poodles wrote:
I get the error "drm device registration failed" using Verizon Media Manager on an android tablet. Any ideas?You get this error if the device is "rooted" (meaing you have full root access). There is an app in the Google Play Store that will temporarily allow you to un-root the device, and when done the registration will work. I use OTA RootKeeper to temporarily un-root and then re-root. The device must be un-rooted each time you attempt to use the Verizon Medai Manager app to view content.

Device registration rules backup

Hi,
I've spent a lot of time putting in device registration rules for different subnets. I'm already backing up the database and also the closest server rules / certificate authority using zman on the (linux) servers.
What I'm not clear on is where the registration rules are held, can anybody advise please?
Thanks in advance,
David

dwhite42,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Identifying the Remote Operator on the Managed Device

I just have one question regarding Remote Management. Since we are using an external VeriSign certificate, the remote operator is currently identified as "unknown user" when a managed device is remote controlled. I think this is working as designed because the Remote Operator's name is derived from the certificate generated on the ZCM server. When External CAs are used (i.e. VeriSign), certificates are not generated for the remote operator, therefore the operator is recorded as an "Unknown User". Am I correct ?
I read the following in the ZCM documentation:
B.3 Identifying the Remote Operator on the Managed Device
When a remote operator launches a remote session on a managed device through ZENworks Control Center, a certificate that helps the managed device to identify the remote operator is automatically generated by ZENworks if an internal CA is used. However, if an external CA is used, the remote operator needs to manually provide the certificate that is chained to the deployed external CA and is certified for SSL Client Authentication. For more information on using the external CA, see Use the Following Key Pair for Identification in Section 2.8, Starting Remote Management Operations. Novell Documentation
If a remote operator launches a remote operation on a managed device without providing a certificate, the name of the remote operator is recorded as An Unknown User in the audit logs, the Visible Signal and the Ask User Permission dialog box. To ensure that the remote operator provides the certificate, deselect Allow Connection When Remote Management Console Does Not Have SSL Certificate in the Remote Management policy.
Do you know how the required key pair for identification is generated ? What are the steps ? We need for the remote operator to be identified.

rguerra,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

ZENworks Asset Management 7.5 - Eval Question

We've been trialing several products and on the ZENworks Asset Managment
evaluation we ran into a few problems.
We run a mostly Mac shop. There are a handful of Windows machines and
plenty of Linux (Redhat & Debian) servers to go around.
I've gotten it all installed and installed the client on one of the OS X 10.5
machines. I see the zamclient running but I'm not even seeing the client
attempt to connect via the Collection Servers -> View Detailed Status window.
In the About ZENworks Asset Management withing the manager it has
license information listed as below.
Workstations 1
UNIX/Linux Workstations 0
Asset Inventory Evaluation
Asset Management Evaluation
UNIX/Linux Evaluation
Does that mean it will only find one workstation in evaluation mode and
that's why my other workstation with the zamclient installed won't show
up?
Thanks in advance,
-Chris

Originally Posted by blcald
Chris,
1st see that the machine conducted an inventory locally on the client. Program files/Novell/Asset Management/bin/Inboxcc/longfilename ending with a wif extension. This doesn't address your issue yet but determine if the client even ran an inventory.
Next run a workstation query with no criteria to see if it shows. If it doesn't I would validate if you have the correct port settings on the client and that it is communicaiton to the collection server. The collection server will aslo have a log (something like collsvrcore and you should see the machine name in there as it talks to the client. If you're in there then determine if you have rights between the DB and collection server correct or that the port settings are correct.
I know this better actually doing than writing it here so others might provide you a more logical approach to troubleshoot. I will check in again later to see how you progressed.
Thanks, Bryant
I do appreciate your response, I'm sure all of that information will come in
handy when I do get a good evaluation license from them that allows Linux
and UNIX support.
I finally reached some folks at Novell and got a little bit of pre-sales support.
From the sound of what they're telling me the evaluation license does not
turn on the linux/unix support and so I couldn't complete my evaluation
with it due to that. I've been working with them to get a more functional
evaluation.

Zenworks patch management and databases

Are there any known issues of Zenworks patch management deployment and corruption of Zenworks database? What would be best practices of Patch Managment and the Zenworks database?

Originally Posted by craig_wilson
Keep the Data Retention for Dashboard data low.
(No more than 30-60 days.)
Otherwise this table can grow very large and cause issues.
I believe 11.3 will have some redesign that will reduce the overhead
with that table and perhaps allow for longer retentions.
On 8/22/2013 10:46 AM, sflegnc wrote:
>
> Are there any known issues of Zenworks patch management deployment and
> corruption of Zenworks database? What would be best practices of Patch
> Managment and the Zenworks database?
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
And if you have say, 4,000 devices or more, I'd suggest even setting it down to 1 day or 7 days at the max. And set it WHEN you setup ZCM, not afterwards, because the database purge/changing isn't optimized properly (at least for Oracle).
Even with 7 days for us, it takes forever to delete a workstation/device along with a slew of other things. But Novell is aware of these things, and hopefully 11.3 will address most of the speed/performance issues.

Zenworks mobile management activesync with datasynchronizer

Can I point zenworks mobile management server at the datasynchronizer as an activesync for auto enrolment?

Georg,
Option A seems to work reliably today with Exchange 2007 so as long as the DataSync team properly implements the settings request for email address provided in the ActiveSync 12.1 protocol then it should work reliably. As for B today if the device doesn't support 12.1 or the server doesn't support 12.1 as is the case right now the only approach we currently have is to strip off the domain from the email address and attempt authentication as the user specified in the email. We are working to see if there is some other approach we can take once we provide additional LDAP enhancements in the next version of the product. But for now the two options you identified in our long term solution are the knowns. I'll forward this thread on to both the DataSync team and the ZMM development team and see if we can all come up with some better ideas.
Thanks,
Jason
>>> Georg Fritsch<[email protected]> 8/9/2012 1:24 PM >>>
Hi Jason,
Thanx again for the detailed and competent anwser.
All this restrictions unfortunately mean that hands-off enrollment is going
to fail for many setups. (including us)
A requirement that the local-part of an email address has to match the
username is ridiculous. (Yes, we all know that Exchange 2003 and ActiveSync
2.5 are ****...)
I am not sure if understand the long term solution:
A) If a user gives just a username, the device must get the corresponding
email address from the ActiveSync system. Available with protocol version
12.1. Fine. (As long as the device uses protocol version 12.1)
B) A user gives an email-address, the username must be derived from the
local-part. Where/How?, local-part == username is an invalid assumptionand
the device does the parsing and just returns the local-part as username to
the ActiveSync system. (And this information is IMO not enough to find the
real username)
Or is B) not allowed (or a really bad idea/design decision) as A) does
reliably work?
Georg
>>> Jason Blackett<[email protected]> schrieb am 09.08.2012 um 05:35 in
Nachricht <[email protected]>:
> The problem with 1.2.3 is that when you authenticate to the domain with
> the following credentials:
>
> user : bob
> domain : m.comp.com
> server : zmm.comp.com
>
> That the ZMM product currently relies on the activesync provider to tell
> it Bob's email address. If it doesn't receive one then the iOS active
> sync account it creates ends up with an email address of
> m.comp.com\[email protected] which seems to work fine for getting
> email/calendar but not for sending email. This only occurs if you do
> hands-off enrollment because as TASNovell points out the email address
> attribute doesn't get populated in the user, but is a required field when
> creating a user.
>
> The ActiveSync way to fix this is that ActiveSync has to allow the user
> to authenticate with their email address [email protected] for instance. And
> then when it parses that it sends back the username as bob and uses the
> full email address. This is the same capability provided by Microsoft
> Exchange 2003 which implements the same version of ActiveSync as DataSync
> currently. There definitely will be issues if the username portion of the
> email address is not the ActiveSync user account name. In that case hands
> off enrollment will fail and you will have to manually create the account
> or import it from the directory and set the email address attribute.
>
> The long term solution is that DataSync will move to the 12.1 version of
> the ActiveSync protocol which provides a settings call that the agent can
> make to retreive the email address from the ActiveSync system if the user
> didn't provide one. However this is going to take some time. So in the
> short term the datasync team implemented the Exchange 2003 like
> capability allowing user authentiction with email address and then
> parsing the username. This capability will be part of 1.2.4. This issue
> is documented in the ZMM Server Release notes
> (http://www.novell.com/documentation/.../zen_mobile_se
> rver_relnote.pdf) as follows:
>
> "12. Systems where iOS users are interfacing with a Novell GroupWise
> DataSync server must use
> DataSync Update 4 (Mobility 1.2.4) to fully utilize the hands-off
> enrollment functionality. Users need to
> enroll using their entire email address in lieu of their username if
> they are enrolling by the hands-off
> method. Similar processes must be followed to use hands-off enrollment
> when users interface with
> Exchange 2003 or any other mail server running ActiveSync 2.5 protocol.
> A user's username and the
> string of characters to the left of the @ sign in their email address
> must be the same."
>
> Jason
>
>>>> TASNovell<[email protected]> 8/9/2012 8:26 AM >>>
>
> feeling a bit silly not reading the version number. We are running
> datasync v1.2.3.3xxx. ZMM seems to connect fine. Email flows correctly
> to the ios devices through the delivered profile. The only thing that is
> not imported is the email address into the newly created user in ZMM. I
> assume this should be pulled through from LDAP as you have to set the
> attribute up during install.

Re: Zenworks 7 Linux Management Device Registration Issue

Similar Messages

Maybe you are looking for