I just fired up the capacity planning tool that’s all the rage these days.

Nimeona ni rahisi kutumia na haraka inatokana mazingira mteja mimi kazi katika majira hii iliyopita.

Na trepidation baadhi, Mimi taabu mwisho OK kifungo na ilipendekeza kitu ambacho ni pretty sawa na kile sisi alitoa mteja wetu (we actually threw in a second application server for future excel use). I take that to be a good sign and increases my confidence in the tool.

It seems pretty powerful stuff a much better starting point than a blank page.

I like that lets you get into some good detail about the environment. How many users, how you project they will use the system (publishing, collaboration, nk), branch office and connectivity / network capacity between them and the mama server. Good stuff.

It asks broad based questions and then lets you tweak the details for a pretty granular model of your environment.

I hesitated downloading it because I have so many other things to look at it, read and try to digest. I’m glad I did.

It’s an easy two-step process. Download system center capacity planner and then download the SharePoint models. It runs nicely on Windows XP.

Based on my quick impression, I don’t see how it might account for:

• Kutafuta: Total documents, maybe types of documents, languages.
• Excel server: how much, kama wakati wote?
• Forms server: how much, kama wakati wote?
• BDC: how much, kama wakati wote.

Those may be modeled and I just didn’t see them in the 10 minute review.

I will definitely use it at my next client.

If I were not a consultant na badala yake kufanya kazi kwa kampuni halisi :), I’d model my current environment and see how the tool’s recommended model matches up against reality. That would be pretty neat. It could lead to some good infrastructure discussion.

</mwisho>

Mteja wangu hivi karibuni imewekwa kifaa uchawi kutoka Mreteni kwamba inaonekana kubadilishwa Cisco yao ya zamani mtandao mzigo balancer (NLB). At about the same time, sisi imewekwa hotfix kushughulikia tatizo workflow.

siku moja au mbili baadaye, sisi niliona tatizo wakati sisi kupatikana pamoja mtoa huduma (SSP). We could get to it, but we would be challenged for a user ID and password many times on each page. This didn’t happen with the main portal app, nor central administration. Naturally, hatukujua ambayo ya mbili (Mreteni au hotfix) itakuwa suala, ingawa mimi kwa dhati watuhumiwa hotfix, kuhesabia tulikuwa si imewekwa ni haki kabisa.

It turned out that Juniper had some kind of compression setting. Moja ya robed takwimu over in the network group turned that setting off. That solved our problem.

This is not the first time that compression has been the root cause of a SharePoint problem for me. IIS compression adversely affected a 3rd party tool from the good people at The Dot Net Factory for IE 6 browsers (IE 7 browsers kazi bila shida).

Hivyo, add "compression" kwenye orodha ya hatari.

</mwisho>

Mikopo kwa: http://www.elfwood.com/art/s/h/sherry/death_colour.jpg.html