Binding Windows Clients to 10.7 OD Master

Has anyone here been able to bind Windows Clients to a 10.7 OD Master?

syedzaidi.nyc wrote:
http://help.apple.com/advancedserveradmin/mac/10.7/#apd52648A71-571A-433C-81A8-2 A7792333F22
States how one can do this.
@schoysi, however, I have run into the same problem as you. I am getting conflicting responses. The people at Apple were not able to provide an adequate answer and I am confused as heck. Would love to know if anyone has gotten this simple functionality to work. I know that PDC, SAMBA, and WINS are removed from both Windows 7 and 10.7 Server, however, OD is authenticating through DNS which would allow me to think that a Windows user should be able to bind through a domain name.
I would love to get as much help as possible on this. I myself have been trying every situation, and need to know if I am doing anything wrong. I truly appreciate the support.
Thanks,
Syed
The above Apple documentation suggests you can bind a Windows Vista or Windows 7 (but not XP) client to a Lion Server. However it also reads like it is talking about a PDC style domain which like you I thought was not possible with Lion Server.
Lion Server has a totally new written by Apple themselves replacement for Samba. The widely believed reason Apple did this was that when Samba switched to a GPL 3.0 license it made it effectively impossible for Apple to continue using Samba code. As the replacement code in Lion is brand new it does not yet address all needs and is likely to have a number of bugs as well.
One would hope that as time goes on Apple will be improving the new code just like iCal Server made great strides as each version was released.
I don't have a spare PC + Windows license to experiment with and Microsoft's ghastly production activation makes it a pain to redo the same machine several times.
The 'Golden Triangle' approach is definitely stated by Apple to work. This involves connecting a Lion Server to a Windows Active Directory system. One would logically also bind the Windows client to the same Active Directory system but then be able to also access the Mac server with the same account as used in Active Directory.
Of course not everyone has an Active Directory setup nor wants one. Hence in the long run the desire for Apple to eventually provide enough capability to do it all itself. This is in Samba 4 i.e. it is supposed to be able to act as a poor mans Active Directory server, but that is covered by the GPL 3.0 license as mentioned above.

Similar Messages

Need Help Binding Windows Xp clients to 10.5 server for a beginner

Hi
I've setup 10.5 server as a standard config. Which turns out it is a Open Directory Master and SMB role is Standalone Server.
I have been able to bind my 10.4 clients to the server domian using Directory Access and choosing automatic under LDAPv3/config.
So far the Macs are working well.
But I need to get the PC XP workstations on board. Where in XP do I have to go to enter in the info for the server to bind the clients to it? All this is new to me and still learning. The server is pretty basic. Authenticating users and giving them access to the shares.
Thanks
Steve

Hi Dave
Thanks for the tips. I was wondering if you could help me out some more? I have never done any binding on the PC. Macs seem quite easy. I'm having trouble taking the info I have on the Mac and applying it to the correct input on the PC's. Bare with me. I think I am almost there.
I did not have the diradmim account set up. But I do now.
Now I have gotten to my computer/properties/system properties/Computer name
I clicked on the Change button near bottom right
Now I am at this new window.
Computer name: I can put anything I want in here?
Member of: I should check Domain and enter the domain of the server?
(currently in my smb settings on the server I have workgroup set to WORKGROUP. Does this need to change?)
Last question I think. You mentioned the diradmin account on 10.5. Where do I enter this info on the PC.
Sorry for all the questions but having this info would help and get me where I need to be.
Thanks
Steve

Binding XP clients to 10.5 Server

Hi there.
I am trying to bind some xp clients to my 10.5 Server. I have set the server up as an OD master with a PDC.
Mac clients can bind with out a problem, but when trying to bind an xp machine I get an error message that says.
"Insufficient resources exist to complete the requested service"
Now I had this problem the other day when I started setting it up and in the end I created another DIrectory admin user for the windows clients and after some testing it looked like my password for the diradmin user was not liked. It had an ! on the end of it, but when I took the ! the XP machine did bind with out a problem.
Now I am trying to bind another machine and it is coming up with the same issue, but the new windows Directory Admin user is not working for that machine either.
I can't get any help from apple as I don't have a select service agreement that covers windows support so I am having to post here.
The log file is giving me this.
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetgrnam(2040)
odssam_getgrnam gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Groups record for 'LIBRARY$'!
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
2009-09-14 14:21:51.551 opendirectorypdbconfig[81679:713] CFPreferences: user home directory at /private/tmp/99 is unavailable. User domains will be volatile.
no credentials available
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(345)
samr_createuser: Running the command `/usr/bin/opendirectorypdbconfig -c createcomputeraccount -r library$ -n /LDAPv3/127.0.0.1' gave 136
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
[2009/09/14 14:21:51, 1, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(371)
pdbdefault_createuser: failed to add a new account for 'LIBRARY$'
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetgrnam(2040)
odssam_getgrnam gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Groups record for 'LIBRARY$'!
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
2009-09-14 14:22:11.316 opendirectorypdbconfig[81692:713] CFPreferences: user home directory at /private/tmp/99 is unavailable. User domains will be volatile.
no credentials available
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(345)
samr_createuser: Running the command `/usr/bin/opendirectorypdbconfig -c createcomputeraccount -r library$ -n /LDAPv3/127.0.0.1' gave 136
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
[2009/09/14 14:22:11, 1, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(371)
pdbdefault_createuser: failed to add a new account for 'LIBRARY$'
Any help on this would be appreciated.

Well I have had a look and the permissions for the tmp on the server are:
/tmp lrwxr-xr-x 1 root admin 11 Jul 18 10:31 tmp -> private/tmp
On my personal machine and another 10.5 server in the office the permissions are:
/tmp lrwxr-xr-x@ 1 root admin 11 29 Oct 2008 tmp -> private/tmp
The permissions on on /private/tmp are on all the machines:
drwxrwxrwt 6 root wheel 204 Sep 21 11:23 tmp
I have tried another approch, with slightly better results, but still no luck.
I manually created and entry into WGM for the XP machine. Just the name of the machine that is. When I then try bind the XP machine to the server I get the following logs.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
[2009/09/21 12:09:59, 0, pid=8391] /SourceCache/samba/samba-187.8/samba/source/passdb/passdb.c:lookupglobal_samname(596)
User HBC0094$ with invalid SID S-0-0 in passdb
[2009/09/21 12:09:59, 0, pid=8391] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(389)
Could not get RID of fresh user
But still no luck I have run disk permissions repair on it as well.

Using iChat Server with Windows clients in an integrated Active Directory/Open Directory environment

A co-worker (Super Brent) and I were working on using iChat as an internal IM server after having used Openfire for a couple days. The reason for switching was basically that we had a Mac Mini Server that was available so we decided to take this on.
First problem: Knowing whether or not Kerberos was needed for AD/OD integration. We spent a ton of time on this, not knowing a huge amount about AD and with our server administrator on courses, we just kept poking at it and removed Kerberos.
For the AD/OD integration, we first bound the Mac Mini to our Active Directory server. We shut off LDAPv3 support as we only wanted to use the AD functionality. Additionally, we ensured that the search policy in Directory Utility only used Active Directory. Then we created an Open Directory master in the Open Directory service. We enabled a self-signed certificate and trusted it locally. After creating the iChat service, ensure that you use the self-signed SSL Certificate and set authentication to Standard. (no kerberos).
Second problem: Once this was complete, we started to test clients out. We were unable to successfully login using our AD credentials using Spark IM and Pandium IM. After trying nearly 100 different variations of server configs, we decided to try a new client. I installed Miranda IM on my Windows XP machine and tried a few different setups. It turned out that the magic potion was to make sure that the "resource" field was set to "Home" and use SSL for encryption. This resource setting was the deal breaker for the other IM clients as many of them such as Spark and Pandium do not have this as a login option.
We ended up using Pidgin IM as the Windows client of choice as it did have the resource variable and it's interface was the best suited for our environment and users.
I hope this helps someone out there as we spent days looking all over the internet trying to figure this out.
Cheers,
Frenchy and Super Brent

Hi,
iChat Server is not something that I know a great deal about.
I tend to point people to the OS X Server Communities and to look out for posts by Tim Harris.
Thanks for taking the time to post this.
9:58 PM Friday; February 10, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.3)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

SMB Slow connection with upgrade to SnoW Leopard and Windows Clients.

<pre>
Dear,
I have now upgraded my MAC OS X LEOPARD 10,5,8 to new SNOW LEOPARD 10,6,2 and if some problems disappear I have a newer big one !
Now every time a Windows CLient try to connect to a SMB Share of SL server that take a long time about 10-15 seconds to open after that depending on client OS that could be nice for a moment (windows 7 and XP) or browsing stay very slow like for 2003 server connecting to Share on S.Leopard.
Could you please help me.
My SL are the main SMB share computer with all data it is connect like other clients to AD (SBS2003).
I have a SBS2003 server that are Master of Domain
and a Server 2008 acting like Terminal Server also member server of domain.
Here are kind of log I receive from SMBD.LOG: I suppose the Credentials problem when connecting are my explanation but how to avoid that !
2009/11/14 13:37:06, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/reply.c:reply_special(332)
netbios connect: name1=MACSRV name2=NOMAD
2009/11/14 13:37:06, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/reply.c:reply_special(339)
netbios connect: local=macsrv remote=nomad, name type = 0
2009/11/14 13:37:08, 2, pid=64794 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/auth/odsam.dylib' loaded
2009/11/14 13:37:10, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/sesssetup.c:setupnew_vcsession(1273)
setupnew_vcsession: New VC == 0, if NT4.x compatible we would close all old resources.
2009/11/14 13:37:10, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/auth/odsam.dylib' loaded
2009/11/14 13:37:18, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/sesssetup.c:setupnew_vcsession(1273)
setupnew_vcsession: New VC == 0, if NT4.x compatible we would close all old resources.
2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/opendirectory.c:getopendirectoryauthenticator(247)
failed to read DomainAdmin credentials, err=67 fd=15 errno=2
2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/opendirectory.c:opendirectoryuser_auth_and_sessionkey(580)
dsDoDirNodeAuthOnRecordType gave -14091 eDSAuthMethodNotSupported
2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/auth/authodsam.c:opendirectory_smb_pwd_checkntlmv1(387)
opendirectoryuser_auth_and_sessionkey gave -14091 eDSAuthMethodNotSupported
2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/opendirectory.c:getopendirectoryauthenticator(247)
failed to read DomainAdmin credentials, err=67 fd=28 errno=2
2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/auth/auth.c:checkntlmpassword(309)
checkntlmpassword: authentication for user fabrice -> fabrice -> fabrice succeeded
2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/vfs/darwin_streams.dylib' loaded
2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/vfs/darwinacl.dylib' loaded
2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/vfs/notify_kqueue.dylib' loaded
2009/11/14 13:37:28, 1, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/service.c:makeconnectionsnum(1092)
nomad (192.168.2.20) connect to service NetDown initially as user fabrice (uid=501, gid=20) (pid 64803)
I also have some kind of following message:
2009/11/14 13:35:18, 0, pid=64579 /SourceCache/samba/samba-235/samba/source/lib/utilsock.c:readdata(534)
read_data: read failure for 4 bytes to client 192.168.2.20. Error = Connection reset by peer
NOte that initialy I don't have problem with MAC OS Client but to be sure they use SMB I have desactived AFP server on SNOW LEOPARD SERVER and now they can't browse the share in finder but when connection via COMMAND+K and SMB://server/share that give now the same error but a little bit faster than windows clients.
Could you help me to troubleshout that problem ?
Thanks for your help.
Felee
</pre>

Dear CarlosGBA,
So when you put 2 computers of your network in WORKGROUP in place of DOMAIN the 38 others works fine ? Strange ?
I have about 15 computers, some are already in workgroup other are linux smb other MAC, the data server are MAC OS X SL, the problem appear for all windows machines, I have try to dissable NTLMV2 and Kerberos since it is probably the faulty element with opendirectory,but always without success !
I don't know what I can do to trouble shout, I hope next release 10.6.3 come soon and correct about all SMB problem ! Probably a dream only ! Since I ask my self if Apple want to correct something andwhy is this problem let without solutionso long ! For a company it is a big problem.I suppose that Apple never read this forum and never answer our problem ! May be I should contact the support phone to be helped !
Thanks for you help.

10.4.9 as Domain Controller fails daily for Windows clients

I have a 10.4.9 Open Directory Master server which also serves as a PDC for Windows XP clients. Windows clients can log in and get roaming profiles with shared homes for Mac and Windows environments. This all works fine.
But, for the last week, every morning, the Windows clients cannot find the domain. I can replace the /etc/smb.conf file with a saved good file, restart the Windows service and all works fine until the next morning, where it fails again. Simply restarting the Windows service does not help; it needs to be reconfigured with a new smb.conf file.
Mac clients can authenticate and connect via smb. The Windows XP Pro clients are up to date with latest updates, so there could be a problem from that, but the updates don't match the date the problems started. The start of the problem coincided with removing an Open Directory Replica, which was no longer needed. It is probably unrelated, but it is the only change I can think of.
There must be some overnight process which resets some setting. Anyone have an idea?
Thanks for any help!
Mostly Xserve servers Mac OS X (10.4.9) 400 + node Open Directory domain Win & Mac All Mac servers
Macs & PCs (too many!) Mac OS X (10.4.4)
Macs & PCs (too many!) Mac OS X (10.4.4)

Tom,
We destroyed our domain and rejoined all our XP boxes. This did not fix the problem. There appears to be a bug in Apple samba-100.7 (10.4.9).
As a quick fix we extracted the smbd binary and smbd.plist from a 10.4.8 combo update (Note: you could also grab the files from a working 10.4.8 install)...
1. Download the 10.4.8 combo update from http://www.apple.com/support
2. Mount the 10.4.8 update .dmg
3. In Terminal navigate to the folder containing Archive.pax.gz, in our case this was...
cd /Volumes/Mac\ OS\ X\ Server\ 10.4.8\ Combined\ Update/MacOSXSrvrCombo10.4.8PPC.mpkg/Contents/Installers/MacOSXSvrCmbBase10.4.8 PPC.pkg/Contents
4. Copy Archive.pax.gz to a location on your HDD, like Desktop
cp Archive.pax.gz ~/Desktop
5. Unzip Archive.pax.gz
cd ~/Desktop
gunzip Archive.pax.gz
6. Grab a copy of Pacifist and use it to open Archive.pax
7. Using Pacifist, extract (drag and drop) the following files from the archive to your Desktop...
/System/Library/LaunchDaemons/smbd.plist
/usr/sbin/smbd
Note: We are going to replace smb in the next step, best backup the current copies of the above files before proceeding.
8. Open Terminal again...
Stop SMB...
sudo serveradmin stop smb
Replace samba with 10.4.8 version...
sudo cp ~/Desktop/smbd /usr/sbin/smbd
sudo cp ~/Desktop/smbd.plist /System/Library/LaunchDaemons/smbd.plist
9. Restart SMB and the process is complete...
sudo serveradmin start smb
Cheers,
Tim

Windows Clients freeze on file opening and sometimes dont log on,SMB errors

On a mac pro , Leopard 10.5.2 server unlimited, OD master, PDC, SMB shares, im getting ready to shoot the mac, it logs on most of the time, but theres so many problems with network freezing and machines freezing at logon. the smb log shows tonnes of these :
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
and the occasional this :
he/samba/samba-187/samba/source/lib/utilsock.c:get_peeraddr(1232)
getpeername failed. Error was Invalid argument
[2008/06/10 15:52:49, 0, pid=81160] /SourceCache/samba/samba-187/samba/source/lib/utilsock.c:writedata(562)
write_data: write failure in writing to client 192.168.2.14. Error Broken pipe
[2008/06/10 15:52:49, 0, pid=81160] /SourceCache/samba/samba-187/samba/source/lib/utilsock.c:sendsmb(769)
Error writing 4 bytes to client. -1. (Broken pipe)

Hi
If you browse the forum there are a number of posts similar to yours. See here:
http://www.apple.com/support/downloads/macosxserver1053comboupdate.html
I would make sure you have a fallback position first before applying the update as well as going for a manual download rather than using Software Update. By fallback I mean a bootable clone of the Server prior to the update. Try not to clone a 'live' Server.
http://support.apple.com/kb/HT1142
Explains what the update 'fixes'. Of particular interest is:
File Services
Addresses an issue that could cause the AppleFileServer process to stop accepting connections while
consuming most of the available CPU time on the server.
The smb.conf file is updated to include the line "acl check permissions = no" in order to provide
expected permissions behavior for Windows clients connecting to the SMB service.
It's not something I would do but you could forego the update and amend the smb.conf instead.
Tony

OD binding and client Imaging??

Have a question about binding a client station to our OD and using that client
as the master image for our labs. Had the concern that each client that is bound to the OD might need to generate a unique GUID to identify it to the directory service.
My concern was that if a station is unbound from the OD would that unbind
all clients from the OD that were cloned with that image.
The reason i ask is because i know this is an issue with Active Directory integration and each station has to be bound to AD post imaging.
Thanks in Advance!

I'm not saying this is bad advice, just that I've never heard this suggestion. If you use an image to make, say, 100 clients, that's a lot of binding you're doing individually. I've always bound my master image before using netboot to distribute it, so I'm wondering if I've missed something.
Jeff

Windows Client Logons Stop - Auth still works.

I've got this new XServe Intel in at the moment.
It's got Open Directory installed and as a Master, Runs DNS and DHCP, as well as Windows services.
Also runs Emails, IMAP and POP3.
The problem I'm having is that the Windows clients that have been joined to the domain decide to stop working, and says the password is wrong until the you go into ServerAdmin and stop Windows Services and then Start it again.
The thing is, if you try to connect to the machine using SMB from a laptop, it asks for the user and password and you can log in fine and it all works, it's just stopping the actual Logon with the Windows Clients
Emails and things still authenticate fine.
Any ideas, it's driving me nuts, I've checked out the logs with with Password Service, Open Directory, the Samba logs too. Nothing reveals anything to why it would be stopping. I changed all the logging levels to high too.
I've occasionally had PasswordService crash, but it didn't crash this time around when it stopped working.

I can think of 2 reasons why you might have this problem.
1) WINS service is either not running or misconfigured
2) The Master Browser elections are failing (this is also tied to WINS)
I would make certain that WINS is correctly configured and running, then try to find out if another computer on your network is claiming Master Browser status.
I had a similar problem in a network of all NT machines, and it turned out that one of the users was a little too smart for his own good. He had purchased his own copy of NT Server (don't ask me why....) and had installed it as a Standalone Server with a Workgroup name that matched the Domain name of the PDC. Master Browser elections were happening every 15 minutes or so, and people could use the network for about 10 minutes out of every hour.
Good luck chasing down this problem.
-Gregg

How to connect oracle running on RH from windows client

I installed oracle on RHEL4,..everything running well till now...
And suddenly i got a problem, i can't connect from windows to my linux server....
i configured my listener to binding linux server ip host,....and service naming to same ip...
while testing connection i got error message...target host not exist....
Anyone know some similar problem and maybe can help providing solution ? thanks in advance...

This is the configuration on my Linux Server :
[oracle@cybertech admin]$ cat listener.ora
# listener.ora Network Configuration File: /home/oracle/product/10.1.0/db_1/netw
ork/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /home/oracle/product/10.1.0/db_1)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = cybertech)(PORT = 1521))
[oracle@cybertech admin]$ netstat -an|grep 1521|grep tcp | grep -v grep
tcp 0 0 127.0.0.1:1521 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:1521 127.0.0.1:32776 ESTABLISHED
tcp 0 0 127.0.0.1:32776 127.0.0.1:1521 ESTABLISHED
This one was my windows client's TNSNames configuration :
# tnsnames.ora Network Configuration File: C:\oracle\BIToolsHome_1\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.
ORCL =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.200)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
This one was my windows client's listener configuration :
# listener.ora Network Configuration File: C:\oracle\BIToolsHome_1\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
SSL_CLIENT_AUTHENTICATION = FALSE
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = awi)(PORT = 1521))
I tried configuring my linux server host ip to 192.168.0.200 and ping it using tnsping, then i got an error message : "no listener".
should i reconfigure /etc/hosts.conf file to add ip 192.168.0.200..? 'cause there's only one ip "127.0.0.1" in /etc/hosts.conf
thanks for the assistance until now ivan

Cisco Jabber for Windows Client SDK

Is there an SDK for Cisco Jabber for Windows client? I could only find the Web SDK. Are there no other SDKs that would let me control features of the Jabber Windows Client?

And in order to avoid TAPI limitation, they say they have started using Jabber which controls all phone functionalities through an Application User connected to the Call Manager.
Assuming they are referring to the normal Jabber for Windows/Mac/iOS/Android applications then this is wrong. Jabber - the client, not the IM&P servers which are part of the CUCM cluster (if you're familiar with Lync consider CUCM+IM&P servers a Front End Pool) - do not use an Application User at all. When a user starts Jabber, assuming SAML SSO is off, they supply an email address. This is used to find the servers via DNS SRV records, or the Mobile and Remote Access Expressway (roughly analogous to a Lync Edge pool) to tunnel through the firewall. After the email address they are prompted for their End User username and password. This is then used to access several APIs on the server, namely the User Data Service to discover what the user has. This would include what the user has configured/available to them. After this is done the Jabber client does one of three things with respect to phone functionality:
If the user has no phone devices provisioned for them - physical or software - it becomes an IM&P client only.
If the user has a software phone phone provisioned, it registers as that using SIP. In this way Jabber is the actual phone. This is called a CSF device for Jabber Windows/OS X.
If the user has a desk phone assigned to their End User account AND administrative policy is to default to desk phone control, it registers to CTI Manager on the CUCM server to control the user's physical phone.
A user can toggle between option two and three, if appropriately provisioned, but cannot have both simultaneously. In other words, Jabber is either controlling a physical phone over CTI or is a phone itself using SIP. The difference is where the audio/video media is sent from/to.
All of this happens using that human's End User credentials.
Now, if you wanted to have a server control the user's phone - either a physical one or Jabber - you would use the TSP as an interface to CTI Manager on the CUCM server and receive real-time events (e.g. the user went off-hook, the phone is ringing with this caller ID, etc.) and issue commands to that phone (e.g. make a call to X). This is done using an Application User account because the server would need to do this for multiple users simultaneously. If you also use the Super Provider concept, the CUCM administrator doesn't have to take the extra step of associating every phone to your Application User manually. Instead, you can simply issue CTI subscriptions to see any/all device activity you want.
This is all assuming you wanted to do the integration server-side to avoid having to update the Cisco TSP application on every user PC (which also limits your WPF application to machines capable of running the TSP) every time the CUCM administrator patches the servers. If you don't care about that, then you can do this all client-side on the user's PC, and have them supply their End User credentials.
Of course, you could also reconsider the Jabber SDK and just embed the make/receive call functionality directly into your application instead.

Please fix: Common Open File Dialog Box to support Favorites (Follow-up: Better provisioning in the Windows client)

One more thing:
What's missing is favorites is a way to use the favorites space in the Common Open File Dialog Box.
Please obsolete or (re)develop components in Windows, so those components support any new workflows in Windows!
On example of an application where you cannot use Favorites is Adobe Photoshop. It uses the Common Open File Dialog Box in Windows (which does not support Favorites).
Comparing Finder (MacOS) with Windows Explorer - you "seem" to have the option of using favorites to pin folders.
Well, if your application calls Windows to use the Common Open File Dialog Box - it's actually NOT POSSIBLE AT ALL to navigate to the user concepts (user folders) pinned to favorites.
Again, the favorites namespace is completely unused (not provisioned) out-of-the-box. That's may be ok, however it's not fully implemented across Windows and just another example of stuff accumulating up to being unusable.
What's missing is favorites is a way to use the favorites space in the Common Open File Dialog Box.
Ref.: Better provisioning in the Windows client
https://social.technet.microsoft.com/Forums/en-US/dbb2102f-00b7-47ca-88f2-4f88cd9d3409/followup-starting-launching-and-switching-?forum=WinPreview2014Feedback#2aba34e9-6074-4750-8f66-425bdeacc705
https://social.technet.microsoft.com/Forums/en-US/168bb9f9-ab18-42e6-9f20-5e36e71f742c/merging-the-task-bar-and-the-start-screen-area?forum=WinPreview2014Feedback#168bb9f9-ab18-42e6-9f20-5e36e71f742c
https://social.technet.microsoft.com/Forums/en-US/59a5bb6a-0368-4f34-bea4-b9811ac0bf8c/dont-forget-development-of-the-start-screen-remember-virtualization-of-it-too-purpose-is-hud?forum=WinPreview2014Feedback#59a5bb6a-0368-4f34-bea4-b9811ac0bf8c
https://social.technet.microsoft.com/Forums/en-US/c10168fe-a534-44aa-a0ec-e9defc71da5f/better-provisioning-in-windows-client-remember-templates-for-the-start-screen-like-the-need-for?forum=WinPreview2014Feedback#c10168fe-a534-44aa-a0ec-e9defc71da5f

Congrats to Carmelo!
Windows Phone and Windows Store Apps Technical Guru - February 2015
Carmelo La Monica
Windows Phone 8: control Nokia Maps (Part 3)
JH: "Part 3 of the series how to work with the Nokia maps control. As the previous articles this one contains a lot of code snippets and some pictures. Good work!"
Ed Price: "A great topic, a fantastic breakdown of sections with clear descriptions, and a nice mix of code formatting and helpful images! Another stellar article from Carmelo! Great job including the link back at the end to the portal
article!"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

ORA-12571 error while creating packages from Windows clients

Hello,
We are facing the ORA-12571 error while creating / replacing packages from Windows Clients connected to a 8.1.7.2.0 db on a Solaris server.
However, there are
1. no errors in connecting and creating transactions from a Sql session
2. no errors in creating / replacing unwrapped/wrapped small (few lines) packages
3. no errors in connecting from a Unix session (remote telnet sessions inclusive).
This happens only when creating wrapped/unwrapped packages, source code of which is greater than 500 kb approx.
Can somebody help me resolve this issue. Any Help would be greatly appreciated.
Regards.
Lakshmanan, K

Update: I had unintentionally left my custom tablespace in READONLY state after an earlier experiment with transportable tablespaces. After putting the tablespace back into READ WRITE mode and creating a new template, I was successfully able to create a new db from the template.
I'm still a little curious why this procedure wouldn't work properly with a READONLY tablespace, however.
Ben

Windows client error joining with Samba 4.2 Active Directory server

I have a basic samba 4.2 ADC setup on CentOS 7 and I get a RPC server not available whenever I attempt to join a windows client to the domain. The smb.conf is default on created during provisioning. All indicated pre-testing seems to work as expected. The windows client finds the domain and recognizes a valid user or not but the last step of joining the domain ends with the error "Unable to join the Domain RPC server not available. Does anyone have any ideas?
Thanks Paul
This topic first appeared in the Spiceworks Community

I have a scenario for you in active directory when two passwords may be valid:
Old passwords can also work on domain controllers that have not received replication yet from either the domain controller the password was changed on, or the PDC emulator in the domain.
Let's take a scenario where we have a 3 site, 3 domain controller (DC) active directory: Site1 with DC1, site2 with DC2 and site3 with DC3.
The ACS application resides in Site3 and is configured to use DC3 for authentication. We have a user "user1" with a password of "123".
User1 decides to call the helpdesk and changes his password to "456".
The helpdesk uses DC1 to make password changes because they are located in site1. For a period of time (based on replication, which defaults to 3 hours between sites) the 123 password and the 456 password will be
valid.
If the user1 user tries the "123" password it will work until DC3 receives the changed password from normal replication. If user1 tries to use 456, DC3 will flag this as a wrong password, and then check the PDC
emulator of the domain to see if it has received a newer password. The PDC emulator will validate the login, and then trigger an immediate replication with DC3.
Regards,
~JG
Do rate helpful posts

File Transfer From Unix server to Windows Client System Using WebUtil

Hi all,
I want to Transfer a File from Unix Server to Window Client System using Webutil. But below mention code is not working.
DECLARE
     V_Server_Path VARCHAR2(500) := Null;
     V_Client_Path VARCHAR2(500) := Null;
BEGIN
     V_Server_Path := '/proj/oraapps/viper/dev/reports/cache/Saveauftr.txt';
     V_Client_Path := 'C:\Migration\EU_Applications\Lima\OAS_WorkArea\Client\Saveauftr.txt';
     IF WebUtil_File_Transfer.Is_AS_Readable(V_Server_Path) THEN
     IF WebUtil_File_Transfer.AS_To_Client(V_Client_Path,V_Server_Path) THEN
          Message('Downloading the File ..... .... ... .. .');
          Message('Downloading Was Successfull ...');
          Message('File Transfer from Server Was Successfull ...');
     END IF;
END IF;
END;
Can anyone suggest me,Why the above code is not working and what to do for solve the Problem.
Regards
Gany

Hello,
You have more chances to get an answer in the Oracle Forms OTN Forum :
Forms
Regards

Binding Windows Clients to 10.7 OD Master

Similar Messages

Maybe you are looking for