|
|
Hi All,
We have a client for which we currently support a SBS 2003
network of some 25 clients. The client has now acquired 2 remote
sites requiring access to the main site data, using mainly Office 2007 apps.
We
intend to install a W2k3 Terminal server for the remote clients who will
connect using the Remote Web Workplace functionality of
SBS and have user My Documents folders redirected to the SBS server.
We want to use mandatory profiles with the addition
of a 3rd party utility to manage the user profile changes
necessary for these applications to function in a useful
manner for end users.
I would be very grateful for advice others have on using
3rd party profile management s/w. (perhaps in a SBS 2003 environment) in
terms of
ease of use, reliability etc.
Thanks
Colin
|
|
mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
[Quoted Text] > Hi All,
>
> We have a client for which we currently support a SBS 2003
> network of some 25 clients. The client has now acquired 2 remote
> sites requiring access to the main site data, using mainly Office
> 2007 apps. We
> intend to install a W2k3 Terminal server for the remote clients who
> will connect using the Remote Web Workplace functionality of
> SBS and have user My Documents folders redirected to the SBS server.
That sounds good.
> We want to use mandatory profiles with the addition
> of a 3rd party utility to manage the user profile changes
> necessary for these applications to function in a useful
> manner for end users.
Why mandatory profiles? What third party utility and why?
> I would be very grateful for advice others have on using
> 3rd party profile management s/w. (perhaps in a SBS 2003 environment)
> in terms of
> ease of use, reliability etc.
I haven't used anything like this, but i've never needed to. What is it you
wish to manage that you can't manage with the built-in tools?
>
>
> Thanks
>
> Colin
|
|
Appsense rocks
Jeff Pitsch
Microsoft MVP - Terminal Services
mcseman wrote:
[Quoted Text] > Hi All,
>
> We have a client for which we currently support a SBS 2003
> network of some 25 clients. The client has now acquired 2 remote
> sites requiring access to the main site data, using mainly Office 2007 apps.
> We
> intend to install a W2k3 Terminal server for the remote clients who will
> connect using the Remote Web Workplace functionality of
> SBS and have user My Documents folders redirected to the SBS server.
> We want to use mandatory profiles with the addition
> of a 3rd party utility to manage the user profile changes
> necessary for these applications to function in a useful
> manner for end users.
> I would be very grateful for advice others have on using
> 3rd party profile management s/w. (perhaps in a SBS 2003 environment) in
> terms of
> ease of use, reliability etc.
>
>
> Thanks
>
> Colin
|
|
Hi Lanwench
Thanks for replying to my posting. The reason for using mandatory profiles
alongside
a 3rd part profile management utility is to handle parts of the profile that
have to change in order for apps to behave properly, whilst limiting the
chance of profile corruption, which seems to plague many TS administrators,
and also not allowing the users to change any desktop settings. We will be
locking down the TS to the extent that they will only see the My Docs folder
and any sub-folders they ccreate such that all data will be re-directed to
the SBS for nightly backups
I would be very interested in your installation method for a TS
in an SBS 2k3 environment.
1. Do you use a separate TS profile in user properties and is it stored on
the TS itself?
2. Do you see any problems with profile corruption if you implement standard
roaming profiles?
3. Do you use individual roaming profiles for each user.
4. Daily Backups of user roaming profiles?
Our install will support up to 15 remote users using the Office 2007 suite.
Thanks
Colin
"Lanwench [MVP - Exchange]" wrote:
[Quoted Text] > mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
> > Hi All,
> >
> > We have a client for which we currently support a SBS 2003
> > network of some 25 clients. The client has now acquired 2 remote
> > sites requiring access to the main site data, using mainly Office
> > 2007 apps. We
> > intend to install a W2k3 Terminal server for the remote clients who
> > will connect using the Remote Web Workplace functionality of
> > SBS and have user My Documents folders redirected to the SBS server.
>
> That sounds good.
>
> > We want to use mandatory profiles with the addition
> > of a 3rd party utility to manage the user profile changes
> > necessary for these applications to function in a useful
> > manner for end users.
>
> Why mandatory profiles? What third party utility and why?
>
>
> > I would be very grateful for advice others have on using
> > 3rd party profile management s/w. (perhaps in a SBS 2003 environment)
> > in terms of
> > ease of use, reliability etc.
>
> I haven't used anything like this, but i've never needed to. What is it you
> wish to manage that you can't manage with the built-in tools?
> >
> >
> > Thanks
> >
> > Colin
>
>
>
>
|
|
mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
[Quoted Text] > Hi Lanwench
>
> Thanks for replying to my posting. The reason for using mandatory
> profiles alongside
> a 3rd part profile management utility is to handle parts of the
> profile that have to change in order for apps to behave properly,
> whilst limiting the chance of profile corruption, which seems to
> plague many TS administrators
OK. I've never had issues with this, and can always restore a profile from
VSS snapshots or nightly backups anyway if I have to. But your mileage may
vary.
> , and also not allowing the users to
> change any desktop settings.
Group policy locks that down easily. Check out KB 278295 for some help with
locking down a TS box. Remember to set a deny on Administrators or you'll
lock yourself out....
> We will be locking down the TS to the
> extent that they will only see the My Docs folder and any sub-folders
> they ccreate such that all data will be re-directed to the SBS for
> nightly backups
Yes - that's a good thing to do for all your users, not just TS. I would
redirect Desktop & App Data too.
>
> I would be very interested in your installation method for a TS
> in an SBS 2k3 environment.
> 1. Do you use a separate TS profile in user properties
Yes, absolutely - control this via group policy, though, not ADUC. Much
easier if you don't have to remember to manually set it :)
> and is it
> stored on the TS itself?
No; everything is on the file server(s). In your environment that would be
SBS, I imagine.
> 2. Do you see any problems with profile corruption if you implement
> standard roaming profiles?
Yes, because you can't mix 'n match profiles. Always set a TS profile path.
> 3. Do you use individual roaming profiles for each user.
Yes - I use both roaming profiles (for desktop users) and TS profiles (for
TS users). Some users, naturally, have one of each -
\\server\profiles$\%username% and \\server\TSprofiles$\%username%
> 4. Daily Backups of user roaming profiles?
Yep.
>
> Our install will support up to 15 remote users using the Office 2007
> suite.
That should be easy enough to manage.
>
> Thanks
>
> Colin
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
>>> Hi All,
>>>
>>> We have a client for which we currently support a SBS 2003
>>> network of some 25 clients. The client has now acquired 2 remote
>>> sites requiring access to the main site data, using mainly Office
>>> 2007 apps. We
>>> intend to install a W2k3 Terminal server for the remote clients who
>>> will connect using the Remote Web Workplace functionality of
>>> SBS and have user My Documents folders redirected to the SBS
>>> server.
>>
>> That sounds good.
>>
>>> We want to use mandatory profiles with the addition
>>> of a 3rd party utility to manage the user profile changes
>>> necessary for these applications to function in a useful
>>> manner for end users.
>>
>> Why mandatory profiles? What third party utility and why?
>>
>>
>>> I would be very grateful for advice others have on using
>>> 3rd party profile management s/w. (perhaps in a SBS 2003
>>> environment) in terms of
>>> ease of use, reliability etc.
>>
>> I haven't used anything like this, but i've never needed to. What is
>> it you wish to manage that you can't manage with the built-in tools?
>>>
>>>
>>> Thanks
>>>
>>> Colin
|
|
Thanks for your extremely useful replies.
Colin
"Lanwench [MVP - Exchange]" wrote:
[Quoted Text] > mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
> > Hi Lanwench
> >
> > Thanks for replying to my posting. The reason for using mandatory
> > profiles alongside
> > a 3rd part profile management utility is to handle parts of the
> > profile that have to change in order for apps to behave properly,
> > whilst limiting the chance of profile corruption, which seems to
> > plague many TS administrators
>
> OK. I've never had issues with this, and can always restore a profile from
> VSS snapshots or nightly backups anyway if I have to. But your mileage may
> vary.
>
> > , and also not allowing the users to
> > change any desktop settings.
>
> Group policy locks that down easily. Check out KB 278295 for some help with
> locking down a TS box. Remember to set a deny on Administrators or you'll
> lock yourself out....
>
> > We will be locking down the TS to the
> > extent that they will only see the My Docs folder and any sub-folders
> > they ccreate such that all data will be re-directed to the SBS for
> > nightly backups
>
> Yes - that's a good thing to do for all your users, not just TS. I would
> redirect Desktop & App Data too.
> >
> > I would be very interested in your installation method for a TS
> > in an SBS 2k3 environment.
> > 1. Do you use a separate TS profile in user properties
>
> Yes, absolutely - control this via group policy, though, not ADUC. Much
> easier if you don't have to remember to manually set it :)
>
> > and is it
> > stored on the TS itself?
>
> No; everything is on the file server(s). In your environment that would be
> SBS, I imagine.
>
> > 2. Do you see any problems with profile corruption if you implement
> > standard roaming profiles?
>
> Yes, because you can't mix 'n match profiles. Always set a TS profile path.
>
> > 3. Do you use individual roaming profiles for each user.
>
> Yes - I use both roaming profiles (for desktop users) and TS profiles (for
> TS users). Some users, naturally, have one of each -
> \\server\profiles$\%username% and \\server\TSprofiles$\%username%
>
> > 4. Daily Backups of user roaming profiles?
>
> Yep.
> >
> > Our install will support up to 15 remote users using the Office 2007
> > suite.
>
> That should be easy enough to manage.
> >
> > Thanks
> >
> > Colin
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
> >>> Hi All,
> >>>
> >>> We have a client for which we currently support a SBS 2003
> >>> network of some 25 clients. The client has now acquired 2 remote
> >>> sites requiring access to the main site data, using mainly Office
> >>> 2007 apps. We
> >>> intend to install a W2k3 Terminal server for the remote clients who
> >>> will connect using the Remote Web Workplace functionality of
> >>> SBS and have user My Documents folders redirected to the SBS
> >>> server.
> >>
> >> That sounds good.
> >>
> >>> We want to use mandatory profiles with the addition
> >>> of a 3rd party utility to manage the user profile changes
> >>> necessary for these applications to function in a useful
> >>> manner for end users.
> >>
> >> Why mandatory profiles? What third party utility and why?
> >>
> >>
> >>> I would be very grateful for advice others have on using
> >>> 3rd party profile management s/w. (perhaps in a SBS 2003
> >>> environment) in terms of
> >>> ease of use, reliability etc.
> >>
> >> I haven't used anything like this, but i've never needed to. What is
> >> it you wish to manage that you can't manage with the built-in tools?
> >>>
> >>>
> >>> Thanks
> >>>
> >>> Colin
>
>
>
>
|
|
mcseman wrote:
[Quoted Text] > Thanks for your extremely useful replies.
> Colin
>
You're welcome - post back if you need more help. The best group for
SBS-specific questions is microsoft.public.windows.server.sbs, for future
reference - it's always good to xpost there if you're posting to the regular
product newsgroups, as SBS often does things its own way.
> "Lanwench [MVP - Exchange]" wrote:
>
>> mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
>>> Hi Lanwench
>>>
>>> Thanks for replying to my posting. The reason for using mandatory
>>> profiles alongside
>>> a 3rd part profile management utility is to handle parts of the
>>> profile that have to change in order for apps to behave properly,
>>> whilst limiting the chance of profile corruption, which seems to
>>> plague many TS administrators
>>
>> OK. I've never had issues with this, and can always restore a
>> profile from VSS snapshots or nightly backups anyway if I have to.
>> But your mileage may vary.
>>
>>> , and also not allowing the users to
>>> change any desktop settings.
>>
>> Group policy locks that down easily. Check out KB 278295 for some
>> help with locking down a TS box. Remember to set a deny on
>> Administrators or you'll lock yourself out....
>>
>>> We will be locking down the TS to the
>>> extent that they will only see the My Docs folder and any
>>> sub-folders they ccreate such that all data will be re-directed to
>>> the SBS for nightly backups
>>
>> Yes - that's a good thing to do for all your users, not just TS. I
>> would redirect Desktop & App Data too.
>>>
>>> I would be very interested in your installation method for a TS
>>> in an SBS 2k3 environment.
>>> 1. Do you use a separate TS profile in user properties
>>
>> Yes, absolutely - control this via group policy, though, not ADUC.
>> Much easier if you don't have to remember to manually set it :)
>>
>>> and is it
>>> stored on the TS itself?
>>
>> No; everything is on the file server(s). In your environment that
>> would be SBS, I imagine.
>>
>>> 2. Do you see any problems with profile corruption if you implement
>>> standard roaming profiles?
>>
>> Yes, because you can't mix 'n match profiles. Always set a TS
>> profile path.
>>
>>> 3. Do you use individual roaming profiles for each user.
>>
>> Yes - I use both roaming profiles (for desktop users) and TS
>> profiles (for TS users). Some users, naturally, have one of each -
>> \\server\profiles$\%username% and \\server\TSprofiles$\%username%
>>
>>> 4. Daily Backups of user roaming profiles?
>>
>> Yep.
>>>
>>> Our install will support up to 15 remote users using the Office 2007
>>> suite.
>>
>> That should be easy enough to manage.
>>>
>>> Thanks
>>>
>>> Colin
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
>>>>> Hi All,
>>>>>
>>>>> We have a client for which we currently support a SBS 2003
>>>>> network of some 25 clients. The client has now acquired 2 remote
>>>>> sites requiring access to the main site data, using mainly Office
>>>>> 2007 apps. We
>>>>> intend to install a W2k3 Terminal server for the remote clients
>>>>> who will connect using the Remote Web Workplace functionality of
>>>>> SBS and have user My Documents folders redirected to the SBS
>>>>> server.
>>>>
>>>> That sounds good.
>>>>
>>>>> We want to use mandatory profiles with the addition
>>>>> of a 3rd party utility to manage the user profile changes
>>>>> necessary for these applications to function in a useful
>>>>> manner for end users.
>>>>
>>>> Why mandatory profiles? What third party utility and why?
>>>>
>>>>
>>>>> I would be very grateful for advice others have on using
>>>>> 3rd party profile management s/w. (perhaps in a SBS 2003
>>>>> environment) in terms of
>>>>> ease of use, reliability etc.
>>>>
>>>> I haven't used anything like this, but i've never needed to. What
>>>> is it you wish to manage that you can't manage with the built-in
>>>> tools?
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> Colin
|
|
Will try the SBS group also.
Thanks again
Colin
"Lanwench [MVP - Exchange]" wrote:
[Quoted Text] > mcseman wrote:
> > Thanks for your extremely useful replies.
> > Colin
> >
> You're welcome - post back if you need more help. The best group for
> SBS-specific questions is microsoft.public.windows.server.sbs, for future
> reference - it's always good to xpost there if you're posting to the regular
> product newsgroups, as SBS often does things its own way.
>
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
> >>> Hi Lanwench
> >>>
> >>> Thanks for replying to my posting. The reason for using mandatory
> >>> profiles alongside
> >>> a 3rd part profile management utility is to handle parts of the
> >>> profile that have to change in order for apps to behave properly,
> >>> whilst limiting the chance of profile corruption, which seems to
> >>> plague many TS administrators
> >>
> >> OK. I've never had issues with this, and can always restore a
> >> profile from VSS snapshots or nightly backups anyway if I have to.
> >> But your mileage may vary.
> >>
> >>> , and also not allowing the users to
> >>> change any desktop settings.
> >>
> >> Group policy locks that down easily. Check out KB 278295 for some
> >> help with locking down a TS box. Remember to set a deny on
> >> Administrators or you'll lock yourself out....
> >>
> >>> We will be locking down the TS to the
> >>> extent that they will only see the My Docs folder and any
> >>> sub-folders they ccreate such that all data will be re-directed to
> >>> the SBS for nightly backups
> >>
> >> Yes - that's a good thing to do for all your users, not just TS. I
> >> would redirect Desktop & App Data too.
> >>>
> >>> I would be very interested in your installation method for a TS
> >>> in an SBS 2k3 environment.
> >>> 1. Do you use a separate TS profile in user properties
> >>
> >> Yes, absolutely - control this via group policy, though, not ADUC.
> >> Much easier if you don't have to remember to manually set it :)
> >>
> >>> and is it
> >>> stored on the TS itself?
> >>
> >> No; everything is on the file server(s). In your environment that
> >> would be SBS, I imagine.
> >>
> >>> 2. Do you see any problems with profile corruption if you implement
> >>> standard roaming profiles?
> >>
> >> Yes, because you can't mix 'n match profiles. Always set a TS
> >> profile path.
> >>
> >>> 3. Do you use individual roaming profiles for each user.
> >>
> >> Yes - I use both roaming profiles (for desktop users) and TS
> >> profiles (for TS users). Some users, naturally, have one of each -
> >> \\server\profiles$\%username% and \\server\TSprofiles$\%username%
> >>
> >>> 4. Daily Backups of user roaming profiles?
> >>
> >> Yep.
> >>>
> >>> Our install will support up to 15 remote users using the Office 2007
> >>> suite.
> >>
> >> That should be easy enough to manage.
> >>>
> >>> Thanks
> >>>
> >>> Colin
> >>>
> >>> "Lanwench [MVP - Exchange]" wrote:
> >>>
> >>>> mcseman <mcseman[ at ]discussions.microsoft.com> wrote:
> >>>>> Hi All,
> >>>>>
> >>>>> We have a client for which we currently support a SBS 2003
> >>>>> network of some 25 clients. The client has now acquired 2 remote
> >>>>> sites requiring access to the main site data, using mainly Office
> >>>>> 2007 apps. We
> >>>>> intend to install a W2k3 Terminal server for the remote clients
> >>>>> who will connect using the Remote Web Workplace functionality of
> >>>>> SBS and have user My Documents folders redirected to the SBS
> >>>>> server.
> >>>>
> >>>> That sounds good.
> >>>>
> >>>>> We want to use mandatory profiles with the addition
> >>>>> of a 3rd party utility to manage the user profile changes
> >>>>> necessary for these applications to function in a useful
> >>>>> manner for end users.
> >>>>
> >>>> Why mandatory profiles? What third party utility and why?
> >>>>
> >>>>
> >>>>> I would be very grateful for advice others have on using
> >>>>> 3rd party profile management s/w. (perhaps in a SBS 2003
> >>>>> environment) in terms of
> >>>>> ease of use, reliability etc.
> >>>>
> >>>> I haven't used anything like this, but i've never needed to. What
> >>>> is it you wish to manage that you can't manage with the built-in
> >>>> tools?
> >>>>>
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> Colin
>
>
>
>
|
|
|