Re: how do I change the user install wizard to create user folder in different location?

From: Les Connor [SBS Community Member] (les.connor_at_DEL.cfive.ca)
Date: 12/16/04


Date: Thu, 16 Dec 2004 17:34:21 -0600

hey, thanks for posting back.

i was just about to go find a disk set so I could read premiuminstallsteps
;-).

-- 
Les Connor [SBS Community Member]
-----------------------------------------------------------
SBS Rocks !
"Alan Drown" <adrown@NOSPAMsigmalan.com> wrote in message 
news:OpUgnW84EHA.3388@TK2MSFTNGP15.phx.gbl...
> got it.
>
> I wasnt adding the \sharepoint at the end of the servername.......
>
>
> thanks again.
>
>
> :)
>
>
> "Alan Drown" <adrown@NOSPAMsigmalan.com> wrote in message 
> news:elq2yN84EHA.3376@TK2MSFTNGP12.phx.gbl...
>> LOL!
>> Thanks Les!
>> Dont get me wrong,  I appreciate the wizards for certain, especially 
>> since I'm not an expert and there is a lot of complexity involved with 
>> SBS 2003. The part that concerns me is when things dont go right I dont 
>> know what's going on under the hood to fix them.
>>
>> Regarding SQL and Sharepoint,
>> thanks for the info, I'll double check in the compnay web.
>> The last step, is what concerns me ....  step 11,  in "To install SP3a to 
>> the SHAREPOINT instance of SQL Server"  in the premiuminstallsetups.htm 
>> file where I'm suppose  to register the SHAREPOINT instance of SQL Server 
>> within the Enterprise Manager.
>> It doesnt seem to  find SQL server running on this system so I dont have 
>> the ability to manage the SQL database from within Enteprise Manager.
>>
>>
>>
>>
>>
>>
>> "Les Connor [SBS Community Member]" <les.connor@DEL.cfive.ca> wrote in 
>> message news:%23QxLr674EHA.3820@TK2MSFTNGP11.phx.gbl...
>>> Your setup looks fine to me.
>>>
>>> Some people read the instructions in such a way that they install both a 
>>> new instance of sql, plus upgrade the sharepoint instance. That's fine, 
>>> but you don't need the new instance if you're not going to use it. 
>>> That's probably what you see on your other box.
>>>
>>> In any case, if you followed the directions, and your companyweb has the 
>>> search box, you did it right. If search doesn' work, you still did it 
>>> right but just didn't finish reading the instructions - there's a 
>>> sharepoint configuration to enable search to function.
>>>
>>> On the other topic: Never slight the SBS wizards. If you want to keep 
>>> doing things the hard way, and banging your head against the wall, then 
>>> go ahead and ignore them. If you want to find out why you should use 
>>> them (especially if you think you shoudn't), then don't use them and you 
>>> will find out the hard way.
>>>
>>> People who have never actually configured and run all of this stuff on 
>>> one box before can't imagine how important the wizards are nor what they 
>>> do. People who have tried to run all this on one box before, appreciate 
>>> the complexity and functionality of the wizards. The wizards *are* what 
>>> defines SBS and makes it what it is.
>>>
>>> If you want the full product, use the wizards. You are not smarter than 
>>> they are. If you don't use the wizards, don't whine when things don't 
>>> seem to be working. Got it ? ;-).
>>>
>>> (you have heard the 'what's that noise' story about the woodcutters and 
>>> chainsaws, right ?)
>>>
>>> -- 
>>> Les Connor [SBS Community Member]
>>> -----------------------------------------------------------
>>> SBS Rocks !
>>>
>>>
>>> "Alan Drown" <adrown@NOSPAMsigmalan.com> wrote in message 
>>> news:%23PDcmu74EHA.4040@TK2MSFTNGP14.phx.gbl...
>>>> Yes, I'm starting to get  a lot of practice... :)
>>>>
>>>> Relying on the wizards to do things seems to be more of a crutch 
>>>> because then you really dont know whats going on under the hood. 
>>>> Depending on the environment the wizards also seem cause some havoc.
>>>>
>>>> FYI, I reinstalled from scratch using the  Dell OpenManage Server 
>>>> Assistant so all my drivers automatically loaded automatically. This 
>>>> part seemed tp worked fine. During the initial ServerAssistant Setup it 
>>>> also asks for  some initial information  like DNS, DOMAIN, license key, 
>>>> etc.. to  automate   the SBS asetup.
>>>>
>>>> On to new  challenges!  :)
>>>>
>>>> SQL 2000 and Sharepoint.
>>>>
>>>> I decided to load SQL 2000 from the premium CD after all was up and 
>>>> running.
>>>>
>>>>
>>>> I followed the directions of updating an existing MSDE installation, 
>>>> selecting the SHAREPOINT instance and not SBSMONITORING per the 
>>>> instructions
>>>> I loaded SP3 and did the same thing, also selecting full text searching 
>>>> and monitoring tools .
>>>>
>>>>
>>>> It loaded without any errors.
>>>> I'm uncertain whether it's running with SQL  server as its backend or 
>>>> still using the MSDE engine.
>>>>
>>>> I'm not able to open SQL server  from Enterprise Manager
>>>> Maybe I should have done an update and should have done a new instance 
>>>> of SQL server???
>>>>
>>>> In add/remove programs  I find the the following relevant programs 
>>>> installed:
>>>> Micorosft SQL Server 2000 (SHAREPOINT)
>>>> Microsoft SQL Server Desktop Engine (SBSMONITORING)
>>>> Microsoft Windows SharePoint Services 2.0
>>>>
>>>> If I look at the services that are running  on the SBS box  :
>>>>
>>>> MSSQL$SBSMONITORING
>>>> MSSQL$SHAREPOINT   both are started and setup to run Automatically
>>>>
>>>> Also in services I see :( dont know if these need to be running or not)
>>>> SQLAgent$SBSMONITORING
>>>> SQLAgent$SHAREPOINT
>>>>
>>>> only SBSMONITORING is running though they're both setup to run 
>>>> automatically.
>>>>
>>>> When I look on a different server running 2003 server with SQL 2000,
>>>> I see these services up an running
>>>> MSQL$DATABASENAME
>>>> MSQLSERVER
>>>>
>>>> How come I'm not seeing MSQLSERVER running on the SBS box?
>>>> SQL enterprise manager doesnt recognize that SQL is running on the 
>>>> system locallly . I tried to register the server by name or by local 
>>>> name and either it thinks SQL isnt installed or or it doesnt have 
>>>> privilages to open it. Is it because its looking for the MSQLSERVER 
>>>> process and not finding it?
>>>>
>>>> If I look at the services running I dont see MSQLSERVER like I do on 
>>>> another install which is on just Windows 2003 server and SQL2000
>>>>
>>>> Should I have done an update or a new install of SQL 2000?
>>>> Is this why I cant open  it in the Enterprise Manager for SQL?
>>>> Should I be able to manage the database from Enterprise Manager for 
>>>> SQL?
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> Alan
>>>>
>>>>
>>>> "Les Connor [SBS Community Member]" <les.connor@DEL.cfive.ca> wrote in 
>>>> message news:eVrab334EHA.1596@tk2msftngp13.phx.gbl...
>>>>> Yeah .... you do get the opportunity to specify location for all data 
>>>>> folders during the integrated install. It isn't obvious on your first 
>>>>> go-around, because the data files location window comes after the 
>>>>> program files window ...
>>>>>
>>>>> Data file locations specified in the setup is a much more efficient 
>>>>> way of organizing, compared to moving everything after the fact. This 
>>>>> is one of the many small details that one learns by doing test 
>>>>> installs - and an example of why it might take say 3 installs to get 
>>>>> one that you really like and will use for production.
>>>>>
>>>>> Folks that do this for a living have an obvious advantage, the 
>>>>> installation and configuration is well practiced. Everybody has had 
>>>>> their first install sometime - just don't get your expectations out of 
>>>>> line. Those that expect the first, the one and only, installation to 
>>>>> do the job are generally setting themselves up for dissapointment and 
>>>>> frustration.
>>>>>
>>>>> -- 
>>>>> Les Connor [SBS Community Member]
>>>>> -----------------------------------------------------------
>>>>> SBS Rocks !
>>>>>
>>>>>
>>>>> "Alan Drown" <adrown@NOSPAMsigmalan.com> wrote in message 
>>>>> news:eE9L5Yx4EHA.4008@TK2MSFTNGP15.phx.gbl...
>>>>>>I decided it just meant the program files and thought/hoped it would 
>>>>>>ask me location of data folders ..
>>>>>> and low and behold IT DID!!!
>>>>>>
>>>>>>
>>>>>> I LIKE when things do what you they they should!
>>>>>>
>>>>>>
>>>>>> :)
>>>>>>
>>>>>> "Alan Drown" <adrown@NOSPAMsigmalan.com> wrote in message 
>>>>>> news:eS%239eJx4EHA.2964@TK2MSFTNGP15.phx.gbl...
>>>>>>> Hi Les,
>>>>>>>
>>>>>>> Well.... It may have, I didnt get to the point of actually adding 
>>>>>>> additional users to find out.
>>>>>>> I decided to rebuild the system. I thought it would be good to be 
>>>>>>> familiar with this systems nuances now than later.
>>>>>>> I had been debating on rebuilding from scratch and then I started 
>>>>>>> having problem logging in and noticed
>>>>>>> upon reboot earlier today  it took forever to log into the sysetm . 
>>>>>>> I looked at the log and there were some strange errors that  just 
>>>>>>> started cropping up yesterday stating
>>>>>>> "Windows cannot access the file gpt.ini for GPO 
>>>>>>> CN={31B2F340-016D-11D2-945 blah blah blah......
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> that kind of sealed the rebuild decision.
>>>>>>>
>>>>>>> just a little background....
>>>>>>> I think I probably created the problem but it's funny that it took 
>>>>>>> so long to crop up. Originally, I had two interfaces configured and 
>>>>>>> then decided for migration purposes it would be easier to just have 
>>>>>>> one interface active since this system isnt in production yet. I 
>>>>>>> disabled the interfaces and didnt rerun the ICW.  After the fact I 
>>>>>>> reran the ICW to let it know it only had one interface but I still 
>>>>>>> had the latency problems at login and the above error in the 
>>>>>>> application log...
>>>>>>>
>>>>>>>
>>>>>>> So that said,
>>>>>>> I'm at the screen in the install process where it wants to know what 
>>>>>>> applications and tools to install.
>>>>>>> I have the option of changing the path here but this looks like for 
>>>>>>> the applications themselves.
>>>>>>>
>>>>>>> If I want the various data files to live some where else, is this 
>>>>>>> where I do it or will I have the opportunity to tell it later on in 
>>>>>>> the installation where the data is to reside - i.e Exchange 
>>>>>>> transaction Logs on D, Information stores on E.?
>>>>>>>
>>>>>>>
>>>>>>> TIA
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> "Les Connor [SBS Community Member]" <les.connor@DEL.cfive.ca> wrote 
>>>>>>> in message news:uD$1MYv4EHA.2288@TK2MSFTNGP11.phx.gbl...
>>>>>>>> Hi Alan,
>>>>>>>>
>>>>>>>> If you followed the document, then the wizard knows already ;-).
>>>>>>>>
>>>>>>>> (because the name and permissions for the 'Users' share are 
>>>>>>>> re-created, that's all the wizard needs)
>>>>>>>>
>>>>>>>> Is it not working correctly ?
>>>>>>>>
>>>>>>>> -- 
>>>>>>>> Les Connor [SBS Community Member]
>>>>>>>> -----------------------------------------------------------
>>>>>>>> SBS Rocks !
>>>>>>>>
>>>>>>>>
>>>>>>>> "Alan Drown" <adrown@NOSPAMsigmalan.com> wrote in message 
>>>>>>>> news:%23KhSkpu4EHA.2192@TK2MSFTNGP14.phx.gbl...
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> Les Connor provided info on migrating the various data folders to 
>>>>>>>>> a new location , thank you very much, but I was wondering if 
>>>>>>>>> someone could tell me how to change the add user wizard to create 
>>>>>>>>> user folders in the new location rather than the old one?
>>>>>>>>>
>>>>>>>>> TIA
>>>>>>>>> alan
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
> 


Relevant Pages

  • RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not instal
    ... registry keys of the Microsoft SQL server and mail to me for analyze. ... This newsgroup only focuses on SBS technical issues. ... SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not install ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Server 2005 Cluster Setup Quiz
    ... I did test and it did not install the client tools. ... http://www.clusterhelp.com - Cluster Training ... Microsoft SQL Server MVP ... Provide a template on how to read SQL Server 2005 setup log files. ...
    (microsoft.public.sqlserver.clustering)
  • RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not install
    ... registry keys of the Microsoft SQL server and mail to me for analyze. ... This newsgroup only focuses on SBS technical issues. ... SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not install ...
    (microsoft.public.windows.server.sbs)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... I'm not seeing performance issues with the full enchilada installed, and 25 users busy hitting SQL. ... WSUS isn't difficult to uninstall - if you have WSUS v2 (installed with SBS R2) uninstall R2 from add/remove programs. ... How can anyone work with 4 instances of SQL Server on the same box? ...
    (microsoft.public.windows.server.sbs)

Quantcast