Workgroup Manager: Sharing is Greyed Out

Having re-built a 10.4.11 Server OS, migrated data from the old drives onto the new ones, installed users, got it up and running, I now find I have a problem where the Sharing icon on the Workgroup Manager is greyed out, and thus I can't get into it to adjust sharing settings, add things, etc.
Currently, users seem to be able to mount all the shared volumes, because they were setup before this issue started, and I turned up the ACL's as well. However, I'm concerned I won't be able to make changes or updates. Is there something I've done or missed that's caused the Sharing to suddenly become greyed out and inaccessaible from Workgroup Manager? And more importantly, is there a way to correct the issue?
Thanks in advance for your insight!

I found the answer to my own question from another discussion:
http://discussions.apple.com/thread.jspa?threadID=1970581&tstart=0
When opening the Workgroup Manager, type in 'localhost' for the address.

Similar Messages

Sharing Icon Greyed Out

Hello, last week we went to setup a new share on our Tiger server 10.4.2 and we found the "Sharing" button in WGM to be greyed out. No matter what we did would get it back. We authenticated, rebuilt permissions, rebooted and nothing seemed to make a difference. I've seen other references to this problem on the forum with no response actually solving the question. Any ideas? Our next step is to run the 10.4.3 upgrades, could this make the problem worse?
Thanks

Can you please confirm wether or not you can edit users? The user list will not be grayed, but if you select a user, the editable options will be. I suspect you have some Open Directory policies that are not being met by Workgroup Manager. Confirm for me first though.
PowerBook G4 12" 867 MHz Mac OS X (10.4.3) 1 GB, 60 GB, AirPort Extreme, Bluetooth

Message recall from shared mailbox greyed out Outlook 2010

Hello,
Can anyone advise if it's possible to recall a message sent from a shared mailbox? The user has full access permissions to the shared mailbox but the 'recall this message' option is greyed out.
We have installed the hotfix below but it says the update is already installed on the system?
http://support.microsoft.com/kb/2475877/en-gb
This is using Windows 8, Outlook 2010 32bit and Exchange 2007 SP3.

Hi,
Try to remove and grant the user the permission to the shared mailbox again to see if the issue still exists.
This issue should have been fixed by kb2475877, please also make sure Office is patched up to date.
We can try with a new profile to setup the account, check if the issue persists:
http://support.microsoft.com/kb/829918/en-us
Regards,
Melon Chen
TechNet Community Support

Yosemite iPhoto 9.6 sharing options greyed out

Hello,
Does anyone else have greyed out sharing options in iPhoto 9.6 on Yosemite?
I am guessing that I will need to delete my preferences but wanted to be sure that I was not missing something else before doing that.
Thanks
Morgs

I would first quit iPhoto and reboot the Mac and see if that changes this
LN

Manage Spaces Tab Greyed Out

I can't access the Manage Spaces tab, it's greyed out. We have opened all the permissions and still can't access the tab. Any suggestions?
Thanks

You must create a user profile with rights in explorer, access the Level Access and create a new profile to explorer, later setting the new profile to user or group.

Manage Metadata is greyed out

Hi,
I am trying to add meta data but unable to see Manage meta data page, it is blank when I click on Manage meta data.
Can any one help

You need to open the metadata file which needs to be modified.
1.Extract the metadata file from the current application.
2. In the manage metadata option open the extracted file.
3. Make the necessary changes.
4. Load the metadata in the application.
Kindly the mark the post as helpful or correct as you find suitable.
Thanks & Regards
Varun

Internet Sharing won't work, greyed out... but not on! Suggestions?

I'm trying to start internet sharing on my MacBookPro (13-inch, Mid 2012).
I'm running Mac OS X Lion 10.7.4 (11E2617).
Ethernet is on and connected. Wifi is on and connected to a created network (which I created to share out my internet).
Why are the options to turn it on greyed out? Any suggestions appreciated, as I'm tearing my hair out here.
Also, the box to turn on internet sharing is greyed out. (a non greyed out box appears as fully white when selected in the list.)
Any help is much appreciated.
Thanks!

Someone help here?

Desktop Manager Greyed Out & Inaccessible

This is a new problem with Desktop manager as I previously had access to it. When I plug my Blacbkberry in and start up Desktop Manager, the full BB Desktop Manager window greys out (inaccessible). The title bar is showing as connected, the server staus (at bottom of BB Desktop Manager window) is online, the actuve device is detected and my Blackberry PIN is shown is the connected device. However, since the entire Desktop Manager box is greyed out, I do not have access to any of the buttons, such as synchronize. When the Blackberry is disconnected from my computer, then I can access the buttons (i.e., the greyed out area is normal again). I followed the Blackberry Trouble Shooting guide online for when the synchronize now button is not available, including uninstalling and reinstalling the software and turning off the antivirus software. I also did all updates for Windows. I'm running Windows 98. Any suggestions? What causes this?

I am also experiencing a very similar situation. I have a Rogers 8310 Curve that syncs to my Win XP Pro laptop using CompanionLink to sync to my Goldmine CRM. I have the original Blackberry Desktop Manager Ver 4.2.0.15 installed. Up until this afternoon, the synchronization has worked perfectly ... never a problem.
During a Sync today, I inadvertandantly unplugged my Curve from the USB cable (forgetting that it was in the middle of a sync). When I plugged the Blacbkberry back in and start the Desktop Manager, the full BB Desktop Manager window greys out (inaccessible). This is the exact same thing as described below:
The title bar is showing as connected, the server staus (at bottom of BB Desktop Manager window) is online, the actuve device is detected and my Blackberry PIN is shown is the connected device. However, since the entire Desktop Manager box is greyed out, I do not have access to any of the buttons, such as synchronize. When the Blackberry is disconnected from my computer, then I can access the buttons (i.e., the greyed out area is normal again).
So, before I go on a fishing expeditition, I'd like to confirm the best course of action. I have a couple of questions:
1) Should I uninstall the Desktop Manager as per the recommendation below?
2) Should any other BB components be removed?
3) When reinstalling, should I use Blackberry DM 4.3 again or would this be the time to update the Desktop Manager Software?
4) If I should update the softward, which upgrade version of Desktop Manager can I safely use with this device?
Thanks for your help.
Herb...

Workgroup manager keychain!

when i open workgroup manager, a box came out asking me to enter the username and the password.. and a message under the box shows the following:
(the keychain is currently locked)
i wrote the username and password and i clicked on CONNECT..
it will ask me to put the keychain password..
what i did is, i opened the keychain access inside utilites, it shows three different lines:
LOGIN, SYSTEM & X509ANCHORS
in somehow i unlocked the SYSTEM and X509ANCHORS
but i couldn't unlock the login keychain, it keeps asking for the keychain password..
i beleive i can disable this keychain access if i unlock it, but the thing is i coudn't unlock it..
and one more thing, in the SYSTEM line .. there's 3 lines with the name (DEFAULT), the first one showing this message in RED:
"This certificate is not in the trusted root database"
wat this means, why its in RED !
please advice!!

Niel,
The two links you provided are helpful, particularly the wikipedia link on X509.
The problem isn't that I cannot unlock my keychain; the problem is that many apps are repeatedly asking for the "X509Anchors" password ... but I can't find X509Anchors user nor do I know the password to provide this dialog.
I discovered that this only happens when I login as root, not when I login as admin (even though admin has admin privs...) Maybe this helps diagnose what is going on.
Dual G5 Mac OS X (10.3.9)

Solution: Sharing Greyed in Workgroup Manager

I noticed there were a few different posts on this issue, but none of them with a solution. I would've replied to them but they were archived.
The simple solution is to kill or force quite the process pmTool. pmTool is a helper application for Workgroup Manager. It gets confused after awhile and just needs a fresh start. A restart will accomplish the same thing, but if you're running a busy server like mine, that's not an option.

Hi,
I'm very new to osx server. I am relying on my ICT guy at my school to sort this problem. He cannot fix our greyed out buttons in WGM and is suggesting a fresh/clean install. I cannot let this happen as it means down time and I have kids with coursework deadlines etc....
I have tried restarting the server but this still makes no difference. I will try the other thing you mentioned tomorrow. Is there anything else you can think of? I am running 10.4.8. Would re-installing the OSX server 10.4.8 update cure anything?
We only set this system up 2 weeks ago so I don't have a suitable backup to use instead. The backup has the same problem.
Any help would be most appreciated.
Thanks
Chris

Deploy to single managed server checked and greyed out while performing upgrade to EPM 11.1.2.4

Hi Gurus,
We are trying to upgrade EPM from 11.1.2.2 to EPM 11.1.2.4 and have applied the maintenance release successfully.
Issue:
When we are trying to configure EPM 11.1.2.4 and are providing the same Shared Service database details, at the summary screen, we are not able to uncheck the option "Deploy to Single Managed server" which is checked and is greyed out.
We have tried the following:
1. We updated the HSS_COMPONENT_PROPERTY_VALUE table and updated the PROPERTY_NAME "isCompact" to false.
2. Modified the config.xml file located at EPMSystem/config and epmsystem1/config to remove the property for compactState.
We are still having the issue where we are not able to uncheck the option for Compact Deployment. Any help would be appreciated.
Thanks in advance.

As it is a maintenance release and it deployed as a single managed server then you will not be able to change the deployment type when applying the maintenance release.
There is a procedure to change a deployment type from compact to single managed server that I created as an internal document.
you may want to give it a go but you would need to test this first as this was an in house test that I carried out.
Hyperion Planning - Version 11.1.2.2.300 and later
Information in this document applies to any platform.
Goal
The scenario:
EPM system 11.1.2.3 was configured and deployed as a single managed server compact deployment so that only one JVM was used for all products EPMServer0.
Later on, due to performance issues, the decision was made to go for using a JVM for each product and get rid of the compact deployment.
The administrator went ahead and redeployed the application servers individually into their own JVM.
However everytime the webserver is reconfigured, the weblogicCluster entry in the OHS file mod_wl_ohs has 2 servers, one for EPMSserver running on port 9000 and another server running on the product default port (as if it was being load balanced)
The aim:
It is clear that initial compact deployment has not been cleared from the EPM environment and the aim in this exercise is to clear the registry and the file system so that the compact deployment is removed fromthe EPMenvironment and we are left with the desired configuration Single JVM deployment for earch web application.
Solution
Caution:
Make sure that you take a backup of the following:
- TheFoundation Services database schema backup
- Take a backup of the following folders:
\Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
\Oracle\Middleware\user_projects\domains\EPMSystem\servers
\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
Disclaimer:
This was tested in House and it worked for this specific environment and it may not work for your environment. So the suggestion is to test first in a development environment and make sure that you take the appropriate backups in case it does not go according to plan.
Use at your own discretion.
Procedure:
1- Run the epmsys_registry to generate the Registry report
2- Search through the report for the word applicationServerDeployment with a corresponding value of configured and take the ObjectID number down for any entry of applicationServerDeployment that has a value of Configured
i.e:
Instance Tasks Configuration (INSTANCE_TASKS_CONFIGURATION)
Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7adf
3- use the object ID of each entry you have taken down throughout the Registry HTML Report to manually set it back to Pending using the following procedure:
                Start a command prompt and set the working directory to
                 \Oracle\Middleware\user_projects\epmsystem1\bin
                run the command:
                 epmsys_registry.bat updateproperty #e4b3a86a82c26941S32ef81a1455fe48473S7adf/@applicationServerDeployment=Pending
                Repeat this command for each ObjectID that has its applicationServerDeployment
                 property set to Configured
4- rerun the epmsys_registry.bat to generate the Registry HTML report and search for applicationServerDeployment in the newly generated report to make sure that they are all set to Pending and there none missed (very Important).
5- Search the registry HTML report this time for EPMServer0 which is the default serverName given to the single managed server deployment (there will be multiple entries)
Take note of the first ObjectID entry in the section header: for example
WORKSPACE_WEBAPP (WORKSPACE_WEBAPP)
Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7bd3
- Start a command prompt and set the working directory to
                 \Oracle\Middleware\user_projects\epmsystem1\bin
- run the command:
                 epmsys_registry.bat view #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
-Note the Parents ID in the output:
For example:
Parent 1
NAME - WORKSPACE_LWA
ID - e4b3a86a82c26941S32ef81a1455fe48473S7bd0
TYPE - LOGICAL_WEB_APP
Parent 2
NAME - HOST:BACHVMPS3TR
ID - e4b3a86a82c26941S32ef81a1455fe48473S7ffe
TYPE - HOST
- Note the single child ID:
For Example:
Child 1
NAME - WebLogic 10
ID - e4b3a86a82c26941S32ef81a1455fe48473S7fd6
TYPE - APP_SERVER
Now run the following command to remove the Link between Parent and child:
epmsys_registry removelink #parentObjectID #childObjectID
In this example that would translate to:
To remove the single child1 link to the WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ):
epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd3 #e4b3a86a82c26941S32ef81a1455fe48473S7fd6
And do the following To remove the link between WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ) and Parent1 and Parent2:
epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
#e4b3a86a82c26941S32ef81a1455fe48473S7bd3
epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7ffe
#e4b3a86a82c26941S32ef81a1455fe48473S7bd3
- Now that the link has been removed, delete the WORKSPACE_WEBAPP component using its ObjectID :
epmsys_registry deletecomponent #parentObjectID
In this example:
epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
- Delete also the Parent representing the WORKSPACE_LWA
epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
Note:So we have now deleted the WEBAPP and LWA for workspace.
6- Repeat steps in section No 5 for every WEBAPP with EPMServer0
7- Start the Weblogic admin console and login
Then go to the left panel and Expand Environment -> Server
Click on Lock & Edit -> Select EPMServer0 -> click on Delete and confirm
Activate Changes and Log off
8- Stop the weblogic admin console server
9- Go to the following location and delete the folder EPMServer0:
\Oracle\Middleware\user_projects\domains\EPMSystem\servers
Delete also EPMServer0 from the following location:
\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
10- Start a command prompt and delete the Windows service that was created for EPMServer0 (if using Microsoft Windows Operating System):
Right click on the service 'OracleHyperion EPM Server - Java Web Application (epmssystem1)' and get its service name i.e: HyS9EPMServer_FOUNDATION1
Run the following command: sc delete HyS9EPMServer_FOUNDATION1
11- Launch the EPMSystem configurator and redeploy the web application server to their own JVM
12- Go to the following location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component and rename the file mod_wl_ohs.conf to mod_wl_ohs.conf.old.
13- Copy the unconfigured mod_wl_ohs.conf file from the location C:\Oracle\Middleware\ohs\ohs\conf to the location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
14- Run the EPM System Configurator again and configure the WebServer to reconfigure the OHS configuration file mod_wl_ohs.conf.
Once done then open the mod_wl_ohs.conf file and make sure that there are no servers configured with Port 9000.
15- Start the services and test the workspace

How to you "publish" Bonjour Shared printers using Workgroup Manager?

Dear Friends,
Hello. We have just spend considerable time setting up Mac OS X 10.6.4 server to host some printers to our Mac clients (previously we had used a Windows print server but it was too slow and inflexible). We have the printers we need set-up and shared out as Bonjour Shared printers because that sends out all of the duplex setting we need. I have tried to "publish" these using Workgroup Manager and they do not show up on the list. How do you "publish" these printers using WGM? NOT: We can't just let people select "nearby" printers because we want to set a default and use kerberos security.

Eric T Gadsby wrote:
Anthony,
Thank you for you help. The procedure you outline is what we have attempted to do. We add the Bonjour-shared printers to a client and then open Work Group Manager on the same computer but when you go to the "Printing" pane of "Preferences" the printers do not show under "Available Printers", neither do USB printers.
Hope this clarifies our problem. We would like to use Work Group Manager as advertised but it doesn't seem to be working for us.
Welcome to my world…
This 'bug' has existed for several major versions of Mac OS X Server (10.6, 10.5, and maybe 10.4). I did report it more than once to Apple as an official bug but they don't seem to 'get it' despite my best efforts.
You can do the following
Add a printer directly to a computer running WGM,
Then use WGM to 'push' the printer out to clients,
The model of the printer will then also be pushed out to clients so they automatically select the correct driver but not the correct paper tray/duplex/etc. settings.
You can do the following
Add a Mac OS X Printer Server queue to the computer running WGM (which must not be the same computer acting as the Mac OS X Printer Server) if you do this via the Bonjour advertisement of the queue then it will not get the model, or any settings from the print server.
You can then push this queue out to clients via WGM
You cannot do the following
Add a Mac OS X Printer Server queue to the computer running WGM (which must not be the same computer acting as the Mac OS X Printer Server) if you do this via IPP, then the WGM machine will get the model automatically, but not any paper tray/duplex settings.
However this queue cannot then be seen in WGM and therefore cannot be pushed out to clients.
Apparently doing custom XML, would allow also pushing out printer settings, but this is so far from 'the Macintosh Way' that only a masochist would do it.
This area is one of the few where the Mac is significantly worse than Windows, it is an area that Microsoft (mostly) sorted literally decades ago. Not only in the Windows world can you push the printer model, and the printer settings, but you can even if needed push the entire printer driver out to the (Windows) clients.

Shared folder consistently greyed out in Finder...

I manage a small Mac network for the communications dept of a university. I have several different shared folders set up for different programs/student groups. Anyway, the largest folder (generic Production folder used by the majority of students) shows up greyed out at first when looking for it inside of programs (for example, in Final Cut when looking for a scratch disk or save location). Clicking on another share point or computer and then going back to the folder usually works, although sometimes it takes a minute or so of doing this.
While this isn't really anything more than an annoyance, I would like to know what is causing this behavior and what can be done to prevent it. It seems to only happen with this folder, although I have noticed the homes folder to be greyed out once or twice also. It doesn't happen every time. Is it simply because there is so much data in the folder that it takes a minute for that folder to be read/mounted/whatever for that program (there are LOTS of subfolders and files in that share, as well as the homes folder incidentally), or is there something more going on here?
Running an XServe, managing all iMacs. All systems are 10.6.7, although I've noticed this behavior for as long as I can remember (10.6.5, at least).

The whole thing happened very quickly. It's amazing to me that with all the time spent beta testing this thing that this little glitch was discovered almost instantly by the public. I think it is very difficult to be a software developer these days.
Anyway, I'm glad you got things sorted out.

My problem is that after printing the first photo or picture, when I come to print a second, both the Colour Management and Epson Colour Controls are greyed out and showing No Colour Management

I have recently purchased a Mac computer (updated to Maverick) to go with my Epson Stylus Photo RX500 printer which has given excellent service with my old Windows computer. However, when trying to print pictures or photos via Photoshop Elements 11, the best results I can get are using the Colour Management and Epson Colour controls in the printing options box.
My problem is that after printing the first photo or picture, when I come to print a second, both the Colour Management and Epson Colour Controls are greyed out and showing No Colour Management, The only way I can reset the controls is to shut down the printer and computer and restart.
Could there may be a setting somewhere that I need to adjust please? I have been in touch with Epson and they say that the Epson Colour controls are part of the Photoshop Elements software but a post on the Adobe forum brought no results and I am unable to contact Adobe.
<Edited by Host>

Hello Garry. Thanks for the reply. I guess I should have used a different title from "How do I post a question?" That should come after trying to resolved the colour settings first. However, to answer your question, after experimenting with all the different settings in Photoshop Elements and Epson software, I now start with PSE11 Colour settings then click "no colour management" then after clicking Print, I choose "More Options/Colour Management/Colour Handling/Printer Manages Colour" then I choose "Page Setup/Layout/Colour Matching" which then shows Epson Colour Controls but I also choose "Layout/Colour Management" which then shows "Colour Controls/Mode" I then of course choose an Epson printer profile depending on the paper I am using. I get good results but as I said, the Colour Matching and Colour Controls are then greyed out. Hope that makes sense.

Grey out of MDM managed fields in R/3 4.7 (Interface between R/3 & SRM)

Hi All,
We have requirement for Creation/extension/changing of MMR (MM01/MM02/MM12).
Current Process:
Creation of MMR for certain material types carried out by MDM team from SRM side.In this case these materials replicated from SRM-MDM to R/3 4.7.
In such case core users from R/3 side can able to change MM fields relevent to MDM managed to fields.So that we want to restrict these fields (Replicated from MDM).to further change
The changes to MMR is only from the MDM side.Not from R/3 side
we dicided to make these fields grey out(Not Editble).through ABAP Development
case1:
If we go through standard configuration of field stutus as a grey out from Field selection/Field Reference.based on materials types/Transaction.then we will face problem while replicating master data from MDM to R/3 .this means that
If we r creating/changing materials from MDM side.and replicated to R/3 side.
Because in R/3 side if i make these fields as grey out .It won't take input values while replicating data from MDM to R/3.so i could end up with idoc error.
Finally the above process is excluded
case2:
If want to go through ABAP development,plz guide on this
If any one face this kind of requirement.Plz guide me

closed

Workgroup Manager: Sharing is Greyed Out

Similar Messages

Maybe you are looking for