Workgroup Manager Monitor Resolution

Hello,
I'm trying to run Workgroup Manager on my clamshell iBook 366 indigo, and I recieve a message that I need a larger monitor resolution.
How do I get around this?
All the other server applications run acceptably, except for Workgroup Manager which seems to need a 1024x768 resolution that I don't have.
I tried using Remote Desktop to administer it, but that doesn't work, and I don't know how to connect this old of an iBook to an external display. Is there some way to use 1024x768 as an unsupported screen resolution?
Thanks very much.

You will need a computer that supports a higher screen resolution. The clamshell iBook, although wonderful in many ways, cannot run WorkGroup Manager. It cannot run any recent version of iMovie either. Its screen is just too small.

Similar Messages

My Mac mini no longer detects my monitor resolution

My Mac Mini has stopped being able to detect the resolution of my monitor, which is a 1680x1050 Acer widescreen. 1680x1050 is also no longer a choice of resolutions under 'Displays' in 'System Preferences' so I cannot select my monitor resolution manually. I suspect that there is a bug somewhere in a recent update which has broken support for my monitor. Is there an official channel by which I can report this bug? Has it been reported already? Is there an ETA on a fix? This renders my Mac more or less unusable.
Here's some info about what I'm running:
Hardware Overview:
Model Name:          Mac mini
Model Identifier:          Macmini3,1
Processor Name:          Intel Core 2 Duo
Processor Speed:          2.26 GHz
Number Of Processors:          1
Total Number Of Cores:          2
L2 Cache:          3 MB
Memory:          4 GB
Bus Speed:          1.07 GHz
Boot ROM Version:          MM31.0081.B06
SMC Version (system):          1.35f0
NVIDIA GeForce 9400:
Chipset Model:          NVIDIA GeForce 9400
Type:          GPU
Bus:          PCI
VRAM (Total):          256 MB
Vendor:          NVIDIA (0x10de)
Device ID:          0x0861
Revision ID:          0x00b1
ROM Revision:          3362
Displays:
VGA Display:
Resolution:          800 x 600 @ 60 Hz
Pixel Depth:          32-Bit Color (ARGB8888)
Main Display:          Yes
Mirror:          Off
Online:          Yes
Rotation:          Supported
Display Connector:
Status:          No Display Connected (Ed: There is definitely a display connected. I'm using it to file this report.)
System Software Overview:
System Version:          Mac OS X 10.6.8 (10K549)
Kernel Version:          Darwin 10.8.0
Boot Volume:          Macintosh HD
Boot Mode:          Normal
Computer Name:          siracusa
User Name:          Christopher Rossi (chris)
Secure Virtual Memory:          Not Enabled
64-bit Kernel and Extensions:          No
Time since boot:          4:52

It's unlikely that the upgrades had anything to do with the problem, slim superdrives are just not all that reliable.
You might try a few tricks before taking it in for service or springing for a Mac compatable external DVD drive.
1. Reset the SMC > Resetting the System Management Controller
2. Reset the PRAM > Resetting your Mac's PRAM and NVRAM
3. Clean it, for example with a > Memorex OptiDisc CD/DVD Laser Lens Cleaner

What does this actually mean and how do I fix it: Alert: Error Count Monitor Resolution state Object Hyper-V Virtual Storage Device Has a value

We are getting this alert on a fair few of our VMs with VHDXs and Dynamic VHDs. Everything seems OK but I am not sure what this actually means and what I need to do to resolve the issue. How do I reset the error count if that is what is required? Thanks
in advance.
Alert: Error Count Monitor Resolution state: New
Error Count Monitor Source: MyVm01 Path: MyHost.MyDomain.local;MyHost.MyDomain.local;FE71577B-A2E2-45C0-B757-2FBCEC9311DE Last modified by: System Last modified time: 2/9/2013 2:08:48 PM Alert description: Instance c:-clusterstorage-volume1-MyVm01-virtual
Sat 09/02
To:Administrator
09 February 2013 14:09
Alert: Error Count Monitor
Source: MyVm01
Path: MyHost.MyDomain.local;MyHost.MyDomain.local;FE71577B-A2E2-45C0-B757-2FBCEC9311DE
Last modified by: System
Last modified time: 2/9/2013 2:08:48 PM
Alert description: Instance c:-clusterstorage-volume1-MyVm01-virtual hard disks-MyVm01-DATA02.vhdx
            Object Hyper-V Virtual Storage Device
            Counter Error Count
            Has a value 9
            At time 2013-02-09T14:08:48.0000000+00:00
Darren

But I am getting this alert from SCOM and SCOM has no information about the alert for me to find out what to do - thought that was the point of SCOM to let you know of problems and how to resolve them. :)
The alert is coming from the Error Count Monitor that is part of the Hyper-V Management Pack Extensions (v 4.0.0.0)
I have tried looking in the Event Logs on the Host and there doesn't seem to be any storage related errors there. I am trying to establish if this is a false positive, why it is happening and if it is safe to override and ignore.
There is nothing on the Product Knowledge tab and nothing on the Alert Context other than what I have already mentioned (see below).
Thanks for responding.
Time Sampled:
09/02/2013 14:08:48
Object Name:
Hyper-V Virtual Storage Device
Counter Name:
Error Count
Instance Name:
c:-clusterstorage-volume1-myvm-virtual
hard disks-MyVM-DATA02.vhdx
Value:
9
Darren

Changing monitor resolution with proper aspect ratio

My project size is 800x600 and I wanted to provide an option to the user to change their monitor resolution at 800x600 by clicking on button. I have also planned to do it by using buddy api xtra, and already tested it. The problem is, when I am doing this on a PC with panoramic monitor (native resolution 1920x1080), it got stretched. I know it's very natural (as the aspect ratio has changed ) and I can get it in shape by squeeze the width using 'draw.rect'.
I noticed, there are some PCs with advanced display card that don't even get stretched, but shows the 800x600 resolution in proper aspect ratio by keeping the extra space black both sides. And I don't need to write any further codes (squeeze the width using 'draw.rect') to keep it in shape.
The real problem starts here, I can't able to filter the above situations by any logical means. I wanted to write codes only for the PCs that get stretched, but I didn't able to find any support from Director to determine which type of display card has been attached. I need to know whether it will get stretched, or the display card can able to manage the aspect ratio.
Any one have any solution in this matter?
Please don't hesitate to ask if you need any more info.

Hello handler
If you talking about this kind of thing...
https://forums.adobe.com/message/5773207
search for..... _movie.stage.drawRect = _system.deskTopRectList[1] & _movie.stage.rect = _system.deskTopRectList[1]
You don't need an xtra to change the resolutions - but you do have to work a few things - I tend to use flash text because it scales better.
regards
milky

Win8.1-TV Monitor resolution need 1360x768 only allow 1280x720 & 1920x1080! Works fine in Win7!

Win8.1-TV Monitor resolution, need 1360x768 only allow 1280x720 & 1920x1080! Works fine in Win7!
I replace my win7 pc with a win8.1 pc. the TV monitor I was using with Win7 worked fine with 1360x768 resolution, however I don't have that choice with the Win8.1. I tried for months now with default & custom settings. I think is that Win8.1 sees the
display as Funai TV (Sylvania) where as Win7 as the Intel video display driver.
Some suggest edit the monitor.ini, not sure if that will work!
Any help is appreciated!

Hi, ecscomp,
Based on my research, the resolution of second monitor should be managed by PC's graphic card driver, not Windows. That's to say, if the graphic card driver doesn't had a correspond setting to change display resolution settings, I'm afraid we have no way
to change the resolution to 1366x768.
Thanks for your understanding.
Roger Lu
TechNet Community Support

AD Users not showing up in Workgroup Manager

Hi, I'm configuring a new installation of 10.4 server on an Intel Xserve to integrate with an already existing AD domain and provide group policies to Mac users via OD.
So far, the install has been so smooth, fast, and simple. The Xserve has been joined to the AD domain, Kerberos is running, and I have an active OpenDirectory Master.
Now, when I go to Workgroup Manager, the users in the AD domain do not show up and if I try to authenticate with the same username and password I used to bind to the domain I get the error "The login information is not valid for this server". Also, if I use dscl I can navigate to "/Active Directory/All Domains/Users" but if I try to run ls I get "ls: DS error: eDSCannotAccessSession".

Hi Tim
You are almost there but not quite.
Firstly its not important if the AD Server does not have a reverse pointer. As long as the OD Master does that should be enough. Ultimately it would be better if there was one configured but there is not much you can do about that is there? I doubt very much if the AD Admin is going to want to fiddle with a 'live' DC's DNS Service if its likely to affect his domain?
What I generally do is this:
Make sure SMB Digital Signing is Not Enabled on the AD Server. There should be at least two places where this has to be disabled. If the 'powers that be' have defined SMB Digital Signing then SFM (Services For Macintosh) must be installed. If its 'nada' to both then you will be severely limited in integrating OSX Server and mac clients with AD. Yes of course make sure there is an (A) and Reverse PTR for the mac server. Next bind all mac clients to the AD Server and make sure the AD Server is listed first for Authentication and Contacts, also make sure mac clients are using the AD for authentication. Test and verify a mac client to see if (a) home folders are created and accessed and that mac clients successfully log in. You sometimes don't get the two.
Now turn your attention to OSX Server. Make sure you have (a) reserved a fixed IP address for it in the AD's DHCP Service and you have placed the AD's IP address as the primary IP address in the DNS Server's field in the Network Preferences Pane (b) tested DNS fully and that OS X Server resolves correctly on the forward and reverse pointers for itself. Now bind OSX Server to the AD using the Active Directory plug in in Directory Access and an AD admin account that has authority for the Domain. Launch Workgroup Manager and you should see AD Users and Groups have 'flowed' into the /Active Directory/All Domains node. Quit out of WGM and launch Server Admin. Enable the AFP Service and set the authentication method to Any Method. Select Open Directory and change the Role from Standalone to Open Directory Master. You will be prompted to create the default Directory Administrator account diradmin (UID 1000). You should see the Kerberos Realm and search base fields autofill with the fqdn of the Server. Change both of these to reflect the fqdn of the AD Server. For example if the fqdn of your mac server is osxserver.addomain.com and the windows server is adserver.addomain.com then change the information presented in thos fields to ADSERVER.ADDOMAIN.COM and dc=adserver,dc=addomain,dc=com. As you can see you should only need to change the first part. Click OK or Continue and you should now have an OD Master that is not the KDC (Kerberos has been stopped). This is the state you want it be in before going any further. You can now 'kerberize' the AFP Service you started previously by selecting the kerberize button and using the same AD admin account you used to previously bind the server to the AD. To doublecheck if the AFP Service has been kerberized launch terminal and issue:
sudo kadmin.local -q list_principals
You should see an entry for [email protected] amongst others.
Now launch Directory Access and make sure the server's loopback address is listed in the LDAPv3 plug in. Make sure that the server is listed first in the Authentication and Contacts fields. Quit out of Server Admin and launch WGM. Navigate to the /LDAPv3/127.0.0.1 node and you should see diradmin waiting for you. Open another connection window in WGM and navigate to the /Active Directory/All Domains node. When you authenticate the /LDAPv3 node you use diradmin, when you authenticate the /Active Directory node you use the AD admin account. Create a Group in the /LDAPv3 node select the + icon and toggle between the two nodes as you select users or groups and add them to your /LDAPv3 node. Once you are happy select a preference to manage, apply desired changes and save the changes. This is better done on a client machine with the Server applications installed.
Back to your mac clients. Begin to join these to the LDAP node using the LDAPv3 plug in in Directory Access. Use the Server's IP Address or its FQDN if the DHCP Server is also doling out DNS information to networked clients. Its IP address should be good enough. Don't bother with authenticated binding and make sure clients are not using the OD master for authentication and contacts. Lastly make sure the Active Directory/All Domains and the /LDAPv3/OD Master IP address or fqdn are in that order for browsed directories.
Its best if you have a secure local admin account on all your mac clients and that each mac is named differently. Set this in the Sharing Preferences Pane.
Begin to test. If everything is OK you should now have mac clients logging into home directories controlled by AD as well as OD Managed Preferences being applied.
One final thing. Avoid using .local as the basis for the DNS Service. I realise in your environment you have no control over that. In which case make sure all mac clients have the AD's .local domain name in the Search Domains field in the Network Preferences Pane. If your clients have Leopard installed you should not have to bother as Leopard copes with .local name resolution better than previous versions of the OS.
As ever how successful you are and how long it takes will depend mostly on how well the AD is configured. There is no magic bullet that can be used on the mac side to fix a poorly configured AD environment. If everything is as it should be regarding the AD Server it should not take you longer than 10-20 minutes (after server installation) for the server and possibly 2-3 minutes for each client. It really should not take that long.
Does this help?
Tony

Workgroup Manager missing users running on 10.6.7 client

Strange issue I am coming across while running the most current version of Workgroup Manager (I just downloaded it again to make sure) on a Mac Os X 10.6.7 client! -> I notice that I am missing a lot of users when I log in and the application opens. I have already deleted the corresponding workgroup manager .plist (user/library/preferences) as well but this does not do much other than asking me to enter server and username/password again
Oddly enough ALL the accounts that are "missing" tend to be lower 3digit User ID's only... in fact the ONLY 3digit id that is showing up is my admin account.
Here's the really ODD part - Workgroup manager is only doing this when it is running on a 10.6 client mac! I am running the IDENTICAL version on a 10.5.8 client, logging into the same server, and ALL the missing users magically appear. Using the same server name, same login, same password - So I am pretty sure this issue is only due to some sort of glitch in how Workgroup manager is running on 10.6( my ver is 10.6.7)
AND of course the "missing" user names are still functioning perfectly well w/ clients receiving emails, logging in to folders etc. etc.
I cannot imagine that I am the only person having this issue, and am wondering if Apple or someone else can please give me some guidance as to the source of this problem and hopefully a bug fix / resolution of the same as I don't want to have to downgrade from 10.6 > 10.5 in order to perform user administration on my server (Server is also 10.6.7)
Thanks in advance for your help

You many not know how to do it now, but you will if you follow the instructions in the link. Or you can simply remove the original Home folder you configured in Setup Assistant while logged into the one you migrated. Then re-migrate your Home folder which will now take on the original account username. Then log into the newly migrated Home folder and delete the other one.

Can not locate Workgroup Manager; possibly not installed?

Here's the story:
I'm trying to get my new camera software installed and one of the steps is to launch Image capture.
Image capture gives me an error saying: "No Image Capture Device connected."
Apple says to fix this I need to open Workgroup Manager (in /Applications/Server/) and change some preferences.
But, I can not find Workgroup Manager for the life of me. I used spotlight with no luck. I also don't have a folder in Applications titled Server. This worries me and makes me wonder if the program could have been deleted or not installed at all?
Any suggestions on how to find WgM would be welcome.

Whoa... somebody got confused someplace... I wouldn't guess you are running OSX Server on a MacBook, but the oSX CXlient instead, so no idea how Apple came up wih that solution.
You likely should not have a Server folder there, nor the APP they speak of.
What kind of Camera exactly, and how does it connect?

Disabling Keyboard Shortcuts for LDAP Accounts -Workgroup Manager...

I work in a school and all our students are on LDAP accounts. Recently some of the kids realized that hitting Ctrl-Opt-CMD-8 inverts the screen display. You wouldn't believe the amount of havoc this has created at school, especially when they do it to a kid’s account that doesn't know how to fix it.
Keyboard and Mouse are NOT one of the items under preferences for either groups or accounts in Workgroup Manager. Does anyone know if there is a way around this, or an alternate way of getting rid of the keyboard shortcuts for Universal Access, for either groups or accounts?
Thanks
Mac OS X (10.4.6)

Within the Workgroup Manager pane for Preferences, there is an option to manage Universal access. Within that section, there is a tab for 'Options'. You will want to change that management to 'Always' and leave the box for 'Allow Universal Access Shortcuts' UNchecked. This will, in effect, disable the usage of the shortcuts for a User or a selected Group account.
Hope this helps out!!
www.Admin660.com

I am using 10.6.8 and I cannot get an Imac to appear in workgroup manager, the mac is bound to both AD and OD. I have removed the bindings, rebuilt the mac and also removed it from bot system but still it does not appear in OD in work group manager.

I have a mac which is connected to a network and is bound to both OD and AD with no issues on my server when I try to manage it through Workgroup manager it does not appear.
I have unbound it , removed it from both systems completely and even rebuilt it but it still does not appear in WGM.

If your server is 10.6 and your client is 10.7 you'll have to add it manually to WGM
via mac address. 10.7 clients don"t automatically appear in 10.6 server wgm

Cannot login with a account created with workgroup manager on local box

Hi my name is richard and i recentgly acqquired from one of ,y friends a macbook pro with leopard 10.5.7 and I downloaded the server tools to it because workgroup manager gives me more control over user creation and the like.there are three issues that i am facing right now:
1) I create an account for a user "VERONICA MARS" short name vmars with a password of apple. when I try to login using that account the login window just sits there and shakes its head at me like no no no wrong cridentials.
2) using the same account vmars i try to reset her password using wgm and it says that it cannot reset the password.
3) when i try to create the account it tells me that the home directory cannot be created.
oh and heres a bonus one:
most of the time in wgm it takes forever to get from one tab to the next and ill have to do a force quit to restore my mkac back to normal.
if anyone can help with these issues please respond
thanks in advanced
richard johnson
mac fan for life

Please let us know the username of the account that is giving you trouble.

Unable to authenticate with diradmin in Workgroup Manager

This has happened before, and I have no idea how it got fixed - too many independent variables...
Anyway, I cannot authenticate the OD with diradmin even while using Workgroup Manager directly on the server.
The setup:
SLS 10.6.8
Split-brained DNS
     Both public and private FQDNs are the same (myserver.mydomain.com). External DNS maps machine record to my static public IP address. Using an AirPort Extreme router, port fowarding services that I want open to the server. The router provides DHCP via NAT to the local network, with a fixed private IP assigned to the server. The server is running DNS with the same zones, machine records, services and aliases that the public IP DNS has, except mapped to the fixed private IP. DNS checks out with changeip, etc.
     The server is an OD master. Yesterday I exported it, demoted it, and restored it. All services (mail, web, etc.) seem to work fine (although I admit to not using Kerberos on AFP due to another issue).
     I have a wildcard certificate that is generated by GoDaddy (*.<mydomain>.com) which seems to work fine with the hosted websites.
This is what the password service error log says when I try to log in with diradmin in Workgroup Manager:
Jan 10 2012 14:01:32    AUTH2: {0x4bbe71ca6b8b45670000000200000002, diradmin} DHX authentication succeeded.
Jan 10 2012 14:01:32    KERBEROS-LOGIN-CHECK: user {0x4bbe71ca6b8b45670000000200000002, diradmin} is in good standing.
Jan 10 2012 14:01:32    KERBEROS-LOGIN-CHECK: user {0x4bbe71ca6b8b45670000000200000002, diradmin} authentication succeeded.
Looks good to me. But I still get the "Information Not Valid for This Server" followed by stuff about invalid login ID or password.
I did notice in the LDAP log:
Jan 10 14:13:12 <myserver> slapd[52283]: SASL [conn=18] Failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Key table entry not found)
And at the last bootup in the directory service error log:
2012-01-10 08:52:03 EST - T[0x00007FFF7027ACC0] - DNSServiceProcessResult returned -65563
The other thing I notice when I log into the library in Workgroup Manager FROM THE SERVER, even if I use the FQDN <myserver>.<mydomain>.com that Workgroup Manager says (in the title bar of the window) <myserver>.local.
I have googled the various errors and messages, and I get folks with all sorts of variations ("change the binding options", etc.) none of which either applied or worked.
Help?

Continuing on my quest... I found this Technical note from Apple about re-kerberizing:
http://support.apple.com/kb/HT3655
Interestingly, in step 3 where it says to remove realm information from kdc.conf, there wasn't any of my realm information. Argh!
So I completed all of the steps and executed the slapconfig command. This resulted in:
bash-3.2# slapconfig -kerberize -f --allow_local_realm diradmin <MYREALM>
diradmin's Password:
Could not resolve hostname <MYDOMAIN>
Skipping Kerberos configuration
Sounds like a dreaded DNS problem. It had been working correctly, but changeip -checkhostname confirmed a problem. Turns out that there were EXTERNAL DNS servers in the Network preferences in System Preferences as well as on the router. With my Split-brained DNS this caused problems (thank you again MrHoffman). So I changed them both to my DNS server INTERNAL IP address and added the external ones to the Forwarder IP Address in DNS. Now checkhostname -changeip returns a favorable result.
So after rebooting ran the slapconfig command again and got the same result. Argh. Cleared DNS caches. Still nothing.
So I tried nslookup.
nslookup <mydomain>
Server:                    10.0.8.2
Address:          10.0.8.2#53
** server can't find <mydomain>: SERVFAIL
Where 10.0.8.2 is the fixed INTERNAL IP address.
However, nslookup on using the fixed IP address yields:
bash-3.2# nslookup 10.0.8.2
Server:                    10.0.8.2
Address:          10.0.8.2#53
2.8.0.10.in-addr.arpa          name = <mydomain>.
Scratching head here... changeip -checkhostname works, nslookup on the IP address works, but nslookup on the host name fails.

Open Directory - Unable to login Workgroup Manager

I am unable to login to Workgroup Manager with my diradmin account.
I know the password is correct.
This is on Mac OS X Lion 10.7.2
Everything was working fine last night, but then it stopped functioning. I am able to see all the users, but they are greyed out. When I try to login, I get "The login information is not valid for this server"
The LDAP log shows a bunch of the same errors that it did not show before.
slapd[76]: SASL Failure: GSSAPI Error: Miscellaneous failure.
Please advise. Thank you.
Samson

Try logging in to Workgroup Manager using the local admin account not the diradmin account. If this works, then try accessing the /LDAPv3/127.0.0.1 choice using the diradmin account.

Home Directories can't be deleted in Workgroup Manager

I set up a Home Directory at the ROOT level of my server to test it. I was successful so I "thought" I knew what I was doing.
I needed the Directories to be in my XRaid as that's where the "room" is and I expect to have 15-20 Home Directories.
So I deleted the User folders at the ROOT level and unshared them in Server Admin (prob the WRONG order).
Now the path to the deleted Directories still shows up in Workgroup Manager and the little "negative" sign is grayed out. I see no other way to delete it.
Now I'm stuck as it appears that any time I try to create a new Home Directory, it "saves" quietly but the user folder it creates is only 44k (although it includes all the Home folders). When I attempt a Log-In I get an error:
"You are unable to log in to the user account "jeff" at this time. Logging in to the account failed because an error occurred. The home folder for the user account is located on an AFP or SMB server....."
I tried exporting all my Users, deleting then and importing them... same issue.
Any other ideas??
Thanks

Hi
When you install OSX Server by default it creates and shares Users, Groups and Public. This has been the case ever since 10.2 came out. Leopard Server continues this 'tradition'. If you delete any of these default folders after first unsharing them, the server will complain mightily as well as giving you problems.
If you want require a sharepoint for your users networked home folders to reside elsewhere simply unshare those default folders and create similar folders wherever you want them (an XServe RAID for example), share these and continue doing what you need to do.
Whenever I have had to attend a site where the local admin has deleted these folders more often than not it has required a rebuild - drastic I know. I have had some limited success by stopping all the services and unfortunately this would also mean demotion to Standalone for your OD Master and recreating the default folders (name them the same) at the root level of your server's boot drive. You can do it using the finder or terminal:
sudo mkdir /Users
Then restart the server. If on successful login the icon on the Users folder comes back then you should be OK.
Hope this helps, Tony

Problem with home directories NOT in Users and Workgroup manager

I am setting up a Leopard server (10.5.3) with the users directories in /h1. This is mounted as /Volumes/h1.
It is exported under AFP as /h1.
When I try to get Workgroup manager to create a home directory, I can enter the home directory as:
afp://quattro.innocon.com/h1
path is 'user'
Full path is:
/Network/Servers/quattro.innocon.com/Volumes/h1
However, when I try to log in as this this user, it says that the directory /Network/Servers/quattro.innocon.com/h1/username does not exist.
I cannot seem to figure out why the 'Volumes' part of the full path is being lost.
Any ideas on how to get this right?

have you checked to see if /Network/Servers/quattro.innocon.com exists?
I'm having ALOT of issues with automount not picking up on the mount-maps set by Open Directory.. If anyone has any solutions on this it would be great.

Workgroup Manager Monitor Resolution

Similar Messages

Maybe you are looking for