Re: "Assign Applications to client computers" doesn't work

Hi,
I followed you instructions and still have the same problem.
However, I did find a discrepency in SBS_LOGIN_SCRIPT.bat file. The
share called "Clients" on SBS was originally mapped to a Windows
folder. I had to rename it to "ClientSetup" becuase we wanted to have a
share called "Clients" that mapped to the company clients folder.
However, after renaming the share, the login batch file was not
modified and it was still referring to "Clients" instead of
"ClientSetup" share. I fixed it, rebooted the server, asked the users
to log off and log back in, but still have the same problem.

When I click on Licensing, I get a "snap-in initialization" error that
includes a CLSID. I searched for the CLSID in the registry and found
it:

Default REG_SZ SBSLicSnap Class

When I click on a computer name on the Server Management console, and
select View Properties it tells me it cannot find and if I want to use
the wizard to create one. Even though all the computers that have
joined the domain are listed, they can all pinged and everyone can do
their work (access folders on the server, ...)

In response to your questions:

1. Have the computers been added to SBS domain?
Yes

2. Does the SBS server meet the following limitations:

1) Only one computer in a domain can be running Windows Small
Business
Server 2003.
2) Windows Small Business Server 2003 must be the root of the Active

Directory forest.
3) Windows Small Business Server 2003 cannot trust any other domains.
4) A Windows Small Business Server 2003 domain cannot have any child
domains.
5) Each additional computer running Windows Server 2003 must have a
Windows Small Business Server 2003 client access license (CAL).
6) A Windows Small Business Server 2003 domain can have no more than
75
CALs. You can use CALs for each user or for each device.

It meets all conditions.

There is no sbsnetsetup.txt, but this is the SBSClientApps.log, from
the server:

10/7/2005 10:30 AM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --

10/7/2005 12:00 PM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --

10/7/2005 12:27 PM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --

10/7/2005 2:18 PM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --

10/7/2005 3:02 PM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --

10/8/2005 9:28 AM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --

10/8/2005 10:54 AM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --

10/8/2005 3:29 PM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --

10/14/2005 9:40 AM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --

10/14/2005 10:53 AM
-- Starting AppLnch.exe --
-- calling DwWaitForShell( 45000 )
- CreateMutex() returned valid and didn't already exist -
CheckPreInstall() - Server-Admin Shortcut already
-- Main() - on the SBS server, did the server-side work, exiting --
"Crina Li" wrote:
> Hi Ashkaan,
>
> Thank you for posting in SBS newsgroup.
>
> Regarding the Licensing problem, it may be caused by the permission
> problem. Please add the Domain Admins with Full Control to the Program
> Files\Windows for Small Business Server folder. You can right click the
> folder and then select Properties. You can add it on Security tab. Test to
> see if the problem still persists. Regarding the "Assign applications to
> client computers" problem, it may be caused by the Licensing problem. If
> the Licensing works, try the "Assign applications to client computers"
> again.
>
> If the Licensing works, however "Assign applications to client computers"
> does still not work, I will suggest that you check the integrity of the SBS
> 2K3 Logon script file:
>
> 1. Locate the file SBS_LOGIN_SCRIPT.bat on the SBS server, the
> ''%systemroot%\sysvol\sysvol\(yourdomain name)\scripts'' folder.
>
> 2. Right click SBS_LOGIN_SCRIPT.bat and choose Edit. The line should be:
> \\servername\Clients\Setup\setup.exe /s SBSServername.
>
> 3. If it's not, change it, save the file, and then log off and back on to a
> workstation.
>
> Also I will suggest you check if you have assigned applications to the
> client computers. If no applications are assigned to the clients or if the
> applications have been deployed to the clients, the installation will
> surely not start:
>
> 1. Go to Server Management\Standard Management\Client Computers.
>
> 2. Click on the "Setup Client Applications" link, click Next and check if
> there are applications.
>
> 3. If the applications you want to deploy are not there, you can create one
> and specify the setup executable file for it. Please note that you should
> first make sure the applications' installation folder is shared and
> Everyone has the Read an Execute permissions.
>
> 4. Click the "Assign Applications to Client Computers" link, go through the
> wizard and assign the applications to the client computers.
>
> 5. Ask the users to log off and log on.
>
> If it does not work, to narrow down the problem, would you please help me
> collect the following information?
>
> 1. Have the computers been added to SBS domain?
> 2. Does the SBS server meet the following limitations:
>
> 1) Only one computer in a domain can be running Windows Small Business
> Server 2003.
> 2) Windows Small Business Server 2003 must be the root of the Active
> Directory forest.
> 3) Windows Small Business Server 2003 cannot trust any other domains.
> 4) A Windows Small Business Server 2003 domain cannot have any child
> domains.
> 5) Each additional computer running Windows Server 2003 must have a
> Windows Small Business Server 2003 client access license (CAL).
> 6) A Windows Small Business Server 2003 domain can have no more than 75
> CALs. You can use CALs for each user or for each device.
>
> 3. On the client computers, locate the files sbsnetsetup.txt &
> SBSClientApps.log under the folder ''\program files\Microsoft small
> business server\clients'', and then compress & send them to me
> (v-crinal@xxxxxxxxxxxxx) for analysis.
>
> Hope the information help and I look forward to your reply.
>
> Best regards,
>
> Crina Li (MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
>
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --------------------
> | From: ashkaan57@xxxxxxxxxxx
> | Newsgroups: microsoft.public.windows.server.sbs
> | Subject: Re: "Assign Applications to client computers" doesn't work
> | Date: 13 Oct 2005 15:11:05 -0700
> | Organization: http://groups.google.com
> | |
> | I clicked the "Licensing" on Server Management and this is what I get:
> |
> | The snap-in is not created, it may not be installed properly.
> | Name: Small Business Server Licensing
> | CLSID:{......}
> |
> |

.

Relevant Pages

  • Re: Embedded Software Engineers, needed in Seattle
    ... One of our client companies in Seattle, ... Create editor for NFN content and server application to import content ... Test server for applications relating to each of the aforementioned ... Experience with being part of a creativity workforce and programming ...
    (comp.arch.embedded)
  • Software Developer Lead for New Mobile Device Product
    ... with a client in Austin who has the following opening. ... is in need of a Passionate Software Developer who is hands-on to lead ... commercial work experience in both web and server side applications. ...
    (comp.lang.java.programmer)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • Embedded Software Engineers, needed in Seattle
    ... One of our client companies in Seattle, ... Create editor for NFN content and server application to import content ... Test server for applications relating to each of the aforementioned ... Experience with being part of a creativity workforce and programming ...
    (comp.arch.embedded)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)