Basically that screen shot indicates that you are logging in with a user that doesn't have a menu. So here is what you do:
1. Using your all modules menu find Administration and then select user maintenance. Go in and select your user ID. (You will find your user ID on the lower left of the main screen.)
2. Click on the groups tab and see what groups you are in. If you are not in the everyone group, add it.
3. Save the record and close Dynamics SL completely and then go back in. Your menu should regenerate. (You may have to use show more modules.)
If you don't have Administration or user maintenance available in your all modules menu or if you can't get into the screen, you probably don't have rights for it. So you need to log in as a user who has the rights. Just go up to the Dynamics Logo, click the drop down and select switch user and enter a user and password with administrator rights such as SYSADMIN.
Now a couple pieces of info:
The groups used in Administration are used for two different things, building menus and rights. A group can have a menu and no rights or a group can have rights and no menu or a group can have both rights and a menu. For the menu to be rendered properly you need to be part of a menu group and have rights (either as an individual or as part of a group.)
The everyone group is a system created group that has all the menus. So if you are in this group you will have the menu. I personally don't use the everyone group with my clients because you can't edit it. I.E. you can remove modules you don't own, add custom reports, 3rd party products, etc. Instead I create a menu group named menu and add all the modules that are going to be used. In fact I may remove specific menu items I know are not going to be used within a module.
Then I assign rights through groups that are used strictly for rights and no for menus. The combination of the Menu group and the rights assigned will determine what menu items a particular user will have.
There is one last critical item to be aware of. The menu files are stored on the workstation running Dynamics SL in the folder Users\<user name>\AppData\Roaming\Microsoft Dynamics SL\Menu Cache When you log as yourself the program looks to see if there are any new changes to the menus or rights that would impact you and if so regenerate the menu files. Since you use a Terminal Server, those files would be on the Terminal Server.
So suppose someone took you out of the everyone group and then your menu disappeared and then they put you back in and then logged into DSL as you but on the terminal server as a different user than you. Then DSL would update the files under that user's user folder think that the change to your rights and menus were taken care of. Then your menu files when you log in would not get updated.
The way to fix this is go in and force a change to your rights. For example if you are in the everyone group, remove that group, save and then put it back in a save again. That will tell DSL that your menus need to be generated then log into the TS as yourself and into DSL as yourself.
Good Luck.