The ability to create a case should still exist, as long as your user name has been associated with your account. Using amazing powers of deductive reasoning I figured out what your real name is and looked you up in our customer database. You should be able to create and edit cases without any problem.
As far as the question you've got here, are the policies listed as required, recommended, or optional? Only recommended and optional policies will appear in the software deployment portal, required policies just run.
In regards to opening a case via the web. Yes this still very much an option. On the front page of http://community.landesk.com there will be a link fo "Smart Self-Service Portal". You will then have a couple of options, one of them will be "get help with a new case". Once you click on this link it will prompt you for information about the type of case that you are looking for. Once you fill out that information and submit it you will be given a few articles that match your criteria in hopes that you will find a quick resolution to your issue. If you do not find the sollution to your problem then you will have the option toward the bottom of the solutions to open a new case. There are a few more steps here than there were traditionally, but we hope that this will actually speed up the resolution of your issue.
Now in regards to the policy not showing up in the policy window. There are a couple of things to check. First make sure that the policy deliver method is set to an available method. For example, required polcies will just run and wont show up in the portal. But "always available will show up there" among others. The next thing you need to do is to check the polciy.sync.log (in the ..\Program Files\LANDesk\LDClient directory). What I would do is rename this log to policy.sync.log.old. Then re-run policy.sync.exe and check the log. You should see the policies being downloaded. It would be helpful to see the results of this log.
Please post the details of the polciy.sync.log and let us know the delivery method that you are using.
If your policies are set correctly, than there is good chance the local database on the client is corrupt. We found that this happens a lot and I use a .bat software task that is easy to use and fixes this and many other policy issues.
Once you run this it may take a few minutes to populate the portal, but it you refresh it a few times you should see items appearing in it.
I forgot how to show this as "code", I have also attached it as a text file, just make it a .bat file, and create a sofware package. It is safe to deploy as needed, even it a system is "healthy".
: This script will delete the clients landesk database, recreate it, validate it and clean up
: old xml files/ Any xml files that are still required will repopulate as needed
: this is also good at fixing portal and other policy issues
cmd /c del "c:\documents and settings\all users\application data\landesk\managementsuite\database" /q
del "C:\Documents and Settings\All Users\Application Data\LANDesk\ManagementSuite\landesk\files" /q
del "C:\Documents and Settings\All Users\Application Data\vulScan\*.xml" /q
del "C:\Program Files\LANDesk\LDClient\sdmcache\landesk\files\*.xml" /q
net stop "Landesk Policy Invoker"
"c:\program files\landesk\ldclient\clientdbutil.exe" /create
"c:\program files\landesk\ldclient\clientdbutil.exe" /validate
net start "Landesk Policy Invoker"
EXIT /B 0
clear_client_db.txt 920 bytes
Are you on sp3. If not attach your policy.sync.exe.log to the post. There is a known issue on sp2 systems. It could also be as simple as re-creating your local database on the system in question. Followin the steps James provided.
does anyone know if this maintenance fix is still relevant for 9.0 SP2?