Category Archives: November 2008

Tergum Review on-line personalis Mini-: Mozy

Aliquam responsum

De … ex parte effectus … of working for a giant corporation is that I get a lot press releases in my inbox every month. I’m still new to the EMC world, ita multum haec sunt volutpat, basically, inscrutable. This or that company purchased these or those EMC products, blah blah blah. I’m not complaining. I actually take this as an incentive to learn more about EMC as time goes by so that I better understand the big picture of what EMC is all about (innuere: suus 'fere Information).

ALIQUOTIES, Suspendisse facile iis omnino quorum unus erat Mozy. Mozy is an on-line backup tool. You install a lightweight client on your workstation (laptop in causam meam), dico vobis quod vos volo ut tergum sursum quod cum facit, tunc missis vestri notitia ad aliquam server(s) on the cloud. It does it in the background.

Cucurrit in tergum meum sub initialis 4 hours and according to Mozy is 550MB or so of data. I only backed up "My Documents" (Hinc, relative parva notitia).

Id recurrit (Puto 24 post horas), quidam plus effercio tergum sursum in circuitu 8 minutes. I never noticed it happen. There was no obvious impact on any work I was doing at the time.

EGO did a test user interface satis honestam iterum praebet ad lego lima(s) you want to restore. It was quick, RAPIDUS, informativus … Nescio quid melius esset.

I spoke to one of my colleagues about it who has more experience with online backup. He said that Mozy is good but that it lacks an ability to tell Mozy to do the equivalent of "restore files that I deleted." This is to say that if you don’t know you deleted a fie, aut si non meminimus: sed nomen, Mozy non potest auxilium vobis magis in terminis facile inveniendo id restituere.

They impose a 2GB limit if you just want to use the service for free. It looks like it’s $5/month for unlimited storage.

Imo linea, si quaeratur a me uterentur online tergum Mozy, nunc iure respondeo, "Hell, yes."

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags: ,

View Calendar sorting Items in Kalendario

2 Restituo

I’m using a calendar to track panel discussions on a given day. I have two sessions: morning and afternoon. I want to create a view that shows morning sessions only listed alphabetically via a session ID. This is a little tricky to accomplish (nisi aliquid manifestum adfui).

I can easily create a filtered view showing just that day’s events. The calendar will show all those events and if they all take place on the same hour, it lists them side by side in the hour slot. That’s great. The tricky part is that, per defaltam, it wants to list them in ID format. Ita, if I add "Session 02" and then "Session 01" quod kalendarium, ostendit eis in illo ordine, (i.e, Sessionem 02 et tunc Sessionis 01). To list them in Session ID order, Ego experiri haec:

  1. Configure the view using the web user interface. No luck. There are no options to sort items this way.

    Quoniam id non laborandum, I am now hoping there’s a CAML query somewhere in there that will allow me to override the sort. CQWP lets me make that kind of change, Calendarium maybe etiam voluntatem,?

  2. Excepteur textus partem, look for an "export" muneris … Bzzz! I can’t export its XML. There is no export option.

    I’m still holding out hope that I can find and modify some CAML query. Since I can’t export the web part, id relinquit SharePoint Designer.

  3. I add the calendar web part to a sandbox site and open that site using SharePoint Designer. I look at the markup for the web part and I find what I’m looking for. It’s encoded madness, tamen suus 'ibi: "<ListViewXml …. >encoded insaniam</ListViewXml>". Specie, illic 'hoc gemma:

<Quaero>
<Ubi>
<DateRangesOverlap>
<FieldRef Name="EventDate"/>
<FieldRef Name="EndDate"/>
<FieldRef Name="RecurrenceID"/>
<Value Type="DateTime">
<Mensis />
</Valor>
</DateRangesOverlap>
</Ubi>
<Orderby><FieldRef Name="Session_x0020_ID" /></Orderby>
</Quaero>

(Ego autem decoded &LT;`S &gt scriptor, ipsosque ad multiplex linearum claritatis gratia).

Adde <Orderby> et frenum nunc per cuiuscemodi ID Sessionis, Item ID non internum album.

Abyss tip vel’ proni ad Becky Isserman pro ea commentarium Isha scriptor blog post Sagi: http://www.sharepoint-tips.com/2008/07/caml-sorting-by-file-name.html. I wouldn’t have put the <Orderby> sine ea commodo mauris, in.

Spero scribere sursum screen cum offa mox apertius, sed in re numquam, saltem feci hoc.

</finem>

NJ SharePoint User Coetus conventus Dave Mann … Aut .. Dixit quod Bob

Aliquam responsum

Bob Fox lets us know that Dave Mann, SharePoint workflow genio, Loquitur in concilio NJ SharePoint user coetus die mercurii vesperum, 11/19/08. Don’t miss it. (Miserabile, seniori meo corporatum fuerit scheduled magna coetus conventus Wed nocte et ego deesset eam).

Click here to register adepto magis details.

Hic es nonnullus sessionem details:

Session Title “Deploying Workflows in a Large Scale SharePoint Environment"

Workflow in SharePoint is an exciting new capability. Autem, it is a capability that is often misunderstood when it comes to the impact it has on your environment. For small environments, the out-of-the-box settings, configurations and architectural approach are probably sufficient. But what about an environment that will be processing thousands of documents per day? How can you make sure that those environments will not falter under the load, but still meet SLA’s for performance and responsiveness? This session will explore why focusing on your workflow subsystem is important, and cover the needs of a large scale workflow environment from the farm level down to individual workflow design specifications. Learn why all workflows need to be looked at in light of performance and scalability as well as how to build workflows that scale in an environment that scales, monitor workflow processing and overcome common obstacles. This session will cover architectural guidance for your SharePoint environment as well as specific coding practices to ensure you get the most out of your SharePoint workflows.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags:

SharePoint Features & Solutions Lorem ipsum dolor — U CRUD ne obliviscaris (aut pro re in D)

2 Restituo

Et nos publice consumere multum temporis cogitatione SharePoint solutiones — quam creare illos, quibus uti tool, quod non accidit cum ad explicandam, ipsum timer, scopes, etc. We spend so much time thinking about the up-front bits that it’s easy to forget that we need to retract them as well. Retracting solutions is probably more difficult, Ex consilio prospectus, opinione, than deploying them. Deployment is basically a cookbook affair. Typically, install a pluma, quod maybe nonnullus notitia in a album pluma Receptorem oneratis, that sort of thing. Autem, retractantem, est in potentia ad magis perplexas.

Haec solutio data partum artificiata:

  • Aliquam erat volutpat
  • Definition list
  • Definition Site
  • Notitia in a album
  • Etiam accipientium
  • Formae InfoPath

Sequitur album.

Dum suus 'maximus patet solutio ad Design artificialibus ea quae recte instantiates, it’s just as important to consider the update and delete cases. If your solution creates a new list and populates that list with data, Solutio retro accidit? In some cases, the list should be deleted. In other cases, it should be left intact for historical purposes. Your business requirements will guide you to the right decision.

Ad auxilium cum, create a matrix that lists each artifact your solution deploys to SharePoint. List three columns per artifact, unum pro creo, update and delete. For each case, statuere rectam operationem finis.

This sort of analysis is obviously best done before the solution is ever deployed to a SharePoint farm. Autem, sicut clibanus, it’s never too late to start doing things correctly. Create that matrix and develop a plan to address the missing update/delete scenarios. It may be a hard problem to solve, sed saltem youll 'forsit posui circa buxum.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags:

SharePoint Designer Lorem Ipsum non potestis Obvius “Longinquus” aut “Foreign” Lists

2 Restituo

Hic 'alium communem SharePoint Designer Lorem Ipsum quaestio:

"Can I access (legere / scribere) SharePoint enumerat via workflows quae non morantur in eadem site sicut list se?"

Simplices respondendum est,: No.

Sicut in tot modis, autem, habemus determinare quod (hoc bonum est). The platform lets us create extensions to the produce in many ways, possidet consuetudo actione (mihi parva project videre codeplex hie exemplum,). A custom action lets us do basically anything we want from SharePoint designer workflow. I’m a big fan of this, in facto, cum optimis utriusque mundi facit — est declarativum finem user familiaris excogitatoris pleno profundum. NET compage nostris digitum tips.

Miserabile, si tibi usura SPD, quia ibi est occasio non potest, ut condimentum arcu vales (debitum ad hoc, quod exigit profundam Visual Bulla elit background). I don’t have any good answer to that problem except that you should prevail upon one of your technical co-workers to create the kind of custom action you need. Alternatively, operamini cum vel contrahendi genere resource administratione ad conducenda.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags:

SharePoint super umerum

2 Restituo

Hodie, Per Legebam Mike Walsh scriptor Doce te SharePoint 2007 in 24 Horarum et, incredibili, postero dixit mihi domina solio, "We just implemented SharePoint in our company." It’s "incredible" because people just don’t talk to me on the train 🙂 It’s funny how SharePoint was the catalyst.

The other interesting aspect was that she didn’t realize that there were books on the product. Here comment was along the lines of "It must be pretty important if people are writing books about it." I think everyone reading my blog would agree with that.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags:

Sursum enim fun et utilitatem suus nere temporaria Rectum WFE

Aliquam responsum

Ego eram unus of 20 aut 30 (vel maybe 100?) panelists last night at the Lugduni SharePoint Users Group meeting. Instead of the usual presentation format, Hoc erat in circuitu Q&A between the audience and the panel members. Early on, Michael Lotter introduced me to a new idea and I wanted to share.

An audience member described how his company had paid a consultant to write an application for his company. The consultant wrote it as a console application using the SharePoint object model. Ut ex, this meant that the program had to be run on a server in the farm. This meant that anyone that wanted to use the app would have to log onto the server, do the work and log off. Primo, this wasn’t a problem, but soon, more and more (non-technical) users needed to use the utility. His question was (paraphrasing):

"What are my options? I don’t want to keep letting users log directly onto the server, but they need that functionality."

Michael Lotter suggested that he configure a new virtual machine, join it to the farm as a WFE and let users run the application from there.

This is a pretty stunning idea for me. Generalizing this solution brings to mind the notion of essentially temporary, almost disposable WFE’s. I think it’s a pretty neat concept. This temporary WFE can run a console application that uses the SharePoint object model. You could also use it to run stsadm commands. It doesn’t have to be part of regular local balancing. If it goes down or gets wrecked, you can just spin up a new one. I repeat myself, but I just have to say that I think it’s a really neat idea.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags:

De Servo Muneris non ponit Quaerere — Cur?

2 Restituo

I was chatting today with Agnes Molnar (quia scio quod solum in Hungariam) about a strange search configuration problem. Namely, search was missing from the "services on server" expandent (Fusce Centralis per -> Operationes -> De Servo Muneris).

EGO had a inviso a VM eget mea et apparatus una, we determined that search was not installed on that server. There are probably a few ways to do this, but we did it by confirming that "Office SharePoint Server Search" was missing from the list of services via Start -> Administrative Tools -> Services.

Oddly, the associated .exe *was* on the server ("C:\Program Files\Microsoft Office Servers\12.0\Bin\mssearch.exe").

I did a quick search and found this blog entry: http://msmvps.com/blogs/obts/archive/2006/10/19/189466.aspx

That’s an email chain with this key point:

"I solved this problem. It was my mistake. I choose "Web front end" instead of "Complete" during install."

This was promising, but we weren’t sure if the installer had actually picked WFE instead of complete when installing MOSS.

We checked for the first (earliest) version of the PSCDiagnostics* file in the 12 hive log directory and in there, we found that the installer had, in facto, configured this server to be a web front end. End of story and it had a happy ending.

(Alicubi in linea, Bob Fox got involved, but all I remember him contributing to the discussion was a comment about Fable 2).

Update: Agnes blogs about this subject here: http://dotneteers.net/blogs/aghy/archive/2008/11/06/wfe-vs-complete-installation.aspx

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags:

Questus sunt recruiters paulo infestantibus?

7 Restituo

An me Iustus? I’ve received three or four calls at my house since late September looking for SharePoint work. I’m used to the email solicitations, but these phone calls are a little unnerving. I haven’t had an updated resume on a job site I(like Monster pr Dice) since almost two years ago exactly. And back then, my resume was all about BizTalk and MS CRM. That’s the only place my phone number appears on line anywhere, quantum scio,.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags:

Im 'iustus Disable ad Comments About …

2 Restituo

Sunt in retro me trahere!

Windows Live Spaces doesn’t do a good job protecting me from comment spam. I assume MSFT has good spam detection, but that the spammers are better. The fact remains, autem, ut multo mihi quam ego spam comments adepto realis comments et ego eram iustus reputo EGO eram iens in in septimana vel ut disable comments.

Autem, hodie, Inveni duos optimos comments dicendam post haec (Finitus de Access) et post haec (quaero de limitandi ad documenta, ut opponitur folders). Those comments are so complementary (adde quod amet pretium nostrum), I can’t see disabling comments and thereby closing off that avenue of useful information. Ita, Ive 'abdicavit me esse hominem spam Auceps / cleaner. Live spaces does provide a pretty decent way to clean up comments, sed qui facit quod vult ad dissipabit tempus?

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin