End user able to log in but there is no content listed in the Mobility portal

Logged in to Mobility portal successfully however there is no content listed in the Mobility portal.

In order for mobile device end users to see content in the LANDesk Portal, an administrator must add the user's Active Directory account or a group containing them to a mobile catalog. (This procedure is described in detail in the Mobility Manager User's Guide. For information, see Add mobile device users to a catalog in the User's Guide.)

In addition, LANDesk Portal users need to be granted default rights (Read & Execute, List Folder Contents, and Read) to the Launchpad folder on the core server. In a default installation, the Launchpad folder is located at:

C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\Launchpad

If that does not resolve the issue verbose logging is often needed to detrimine the cause of missing content.

Enable verbose logging for more detail.

On the core server turn logging on:

Go to C:\Program Files(x86)\LANDesk\ManagementSuite\landesk\Launchpad.Cloud\web.config

1. Open the web.config in a text editor.
   1. On line 20:, remove “<!—“
   2. On line 30, remove “0-->”
2. Create c:\log folder and grant everyone read/write access.
3. Log in to the portal
4. Review the log in the c:\log folder

Example log file ( Author has added Bold character to highlight items in the log, true log on core will not have bold characters the names of the domain and server have also been changed)

LOGGING: looking for configurations in 'C:\Program Files (x86)\LANDesk\ManagementSuite\log\config'
LOGGING: checking for C:\Program Files (x86)\LANDesk\ManagementSuite\log\config\LANDesk.ManagementSuite.Database.log4net
LOGGING: checking for C:\Program Files (x86)\LANDesk\ManagementSuite\log\config\LANDesk.ManagementSuite.Diagnostics.log4net
LOGGING: %property{ModuleName} = LANDesk.ManagementSuite.Database.DLL
LOGGING: %property{LogFolder} = C:\Program Files (x86)\LANDesk\ManagementSuite\log
LOGGING: %property{ProcessId} = 3792
Logging Started
http://MDM /landesk/launchpad.core/client.svc/platform/ios/4.3.5/iphone started at 4/16/2012 5:54:21 PM
DirMan Created
DirMan identity: Domain1\Administrator
DirMan - Username: Administrator Domain: Domain1
DirMan - LDAPDomain: DCServer.domain1.com Domain: DCServer
DirMan - Found users domain, continuing search
DirMan - Using path: LDAP://DC=DCServer,DC=Domain1,DC=com
DirMan - Exception while searching domain DCServer - System.DirectoryServices.DirectoryServicesCOMException (0x80072030):

There is no such object on the server.

at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.DirectorySearcher.FindAll(Boolean findMoreThanOne)
at System.DirectoryServices.DirectorySearcher.FindOne()
at LaunchPad.Dependencies.DirMan.GetUserInformation()
DirMan - Did not find any matching users
http://mdm/landesk/launchpad.core/client.svc/platform/ios/4.3.5/iphone finished at 4/16/2012 5:54:22 PM with a total of 213 milliseconds

Conclusion

From this log you can see that it is looking for the user administrator in - LDAPDomain: DCServer.domain1.com Domain: DCServer and Exception while searching domain DCServer (which in this example DCServer is the name of the Domain controller)

The fix to this is to change Directory manager on the core server to read as Domain.com instead of dc.domain.com. This will allow the LDAP search to process through the domain and not local users on the Domain controller (DCServer).