Previously I’ve posted my irritation with Walmart’s ‘rollbacks’ which mostly seemed to be making products stand out by listing the SAME price as a lower price and having a previous fictitious higher price. Well today I am surprised and excited to see a REAL ROLLBACK. Walmart brand milk at the Portsmouth Walmart was $1.98 a gallon!. This was for ALL the different fat levels (1%, 2% & whole milk). Now please note this was at the Portsmouth Walmart Super Center, NOT the Newington Walmart. I was at the Newington Walmart last Thursday and the price of milk there was $2.42 gallon.

I got to thinking about my issues with rollbacks. I’m wondering if the ‘rollback’ is from the price at some other higher-priced Walmart? I really wish the prices were consistent between the different Walmarts.

While I was there killing time I also stocked up on some canned goods and did some price checking. If you’re a fan of regular Tide the Portsmouth Walmart is no longer carrying it, just the Tide 2x. The holiday music was on, Christmas displays are out, but Halloween leftovers are marked 75% off. So if you want to pick up any Hallloween decorations for next year now is the time to pick them up!

On my previous post on Thursday’s shopping I got a comment from another blogging coupon site. I haven’t checked out their links, but it looks like lots of links to online coupons. If you have a minute feel free to check it out!

Happy Shopping!

alphainventions

I see where Ford and the CAW have come to an agreement and concessions were made.  At least the union woke up and smelled the coffee but aren’t happy about the rollbacks – but then who is?

But what bothers me is the up to $100,000 settlements for those being laid off and the vehicle vouchers.  Who the hell pays for that?  Probably the consumer who will have to pay the bill through charges to the vehicles they buy – vehicles which have leaky windows, blowing spark plugs and burning speed controls.

Why are we rewarding these guys with so much money when they can’t build a decent vehicle?  And, don’t even help those consumers shafted with vehicles like that mentioned in my last blog.

And Toyota, I hear is thinking of joining the CAW.  Wake up guys.  You will have to start paying dues and look what happened to the CAW workers in St. Thomas – no work.  Yeah, they are getting big packages but at the cost to the consumer who not only pays for these packages but also pays to repair poorly built vehicles.  You want to be part of that crowd?

At least at Toyota you are doing the right thing.  Just think – join the union and get the big deductions off your new salary.  I saw one group join a union and they made less per week due to the union dues and their company lost the contract to another company who gave all the old workers a 50 cent raise right off the bat. Hmmmm.  Oh, did I mention the new company was non-union?

And, if you join the CAW, will all those CAW workers who are now laid off get an advantage at your plant and claim seniority and get your job?  Just a thought.  I saw guys at GM losing their job at one plant and claiming seniority and moving to another plant and some poor guy got dumped.

So Toyota, you can join the CAW, which are losing members and jobs and help pay the union executives their large salaries and benefits and build sub-standard vehicles or, keep working at Toyota and produce vehicles with some pride in workmanship and know you still have a job. 

Your choice.

alphainventions

http://condron.us/index.php?i=6
condron.us

Galera olha o cenário vc no servidor de um cliente em produção fazendo um delete e sem querer vc esquece do bendito where..
quem nunca passou por algo parecido…
esquecer do where num delete ou update pode trazer muita dor de cabeça, que já passou por isso sabe do que estou falando…
uma maneira de revitar isso é usar o comado rollback…
ele aborta uma transaçao, bom então temos que iniciar uma transação
e como faremos isso no postgres?
bom iniciamos com o comando begin…
simples assim…
depois do comando begin seguimos com nossos sql normalmente pra finalizar uma transação usamos o comando commit, fazendo isso nossos SQLs serão efetivados em disco..
então seria algo assim:
begin;
SQLs;
commit;

vamos aos exemplos, primeiro vamos criar uma database;
pra testes…
create database testes;
após isso vamos nos conectar a base recem criada…
\c testes
agora criando uma tabela pra podermos fazer nossos testes…

create table pessoas(id serial, nome varchar(60), idade int);
agora vamos popular nossa tabela

insert into pessoas(nome, idade) values(‘marcio’, 33);
insert into pessoas(nome, idade) values(‘cheila’, 38);
insert into pessoas(nome, idade) values(‘amanda’, 24);
insert into pessoas(nome, idade) values(‘vitoria’, 08);
insert into pessoas(nome, idade) values(‘gui’, 16);
insert into pessoas(nome, idade) values(‘fox’, 31);

vendo nossos dados na tabela…
testes=# SELECT * from pessoas;
id | nome | idade
—-+———+——-
1 | marcio | 33
2 | cheila | 38
3 | amanda | 24
4 | vitoria | 8
5 | gui | 16
6 | fox | 31
(6 registros)

ok agora vamos a parte que nos interessa
vamos inciar uma transação, deletar alguns registros e voltar atras com rollback
segue o trecho…
testes=# begin;
BEGIN
testes=# DELETE FROM pessoas WHERE id > 3;
DELETE 3
testes=# SELECT * from pessoas;
id | nome | idade
—-+——–+——-
1 | marcio | 33
2 | cheila | 38
3 | amanda | 24
(3 registros)

testes=# ROLLBACK;
ROLLBACK
testes=# SELECT * from pessoas;
id | nome | idade
—-+———+——-
1 | marcio | 33
2 | cheila | 38
3 | amanda | 24
4 | vitoria | 8
5 | gui | 16
6 | fox | 31
(6 registros)

ufá tá tudo ali
viram pra evitar muita dor de cabeça podemos fazer com uma transação, não custa iniciar com um simples begin né…
agora se tudo tiver corrido bem basta dar um commit no final e tudo será gravado no banco, mas tenha certeza que tudo foi feito conforme vc queria mesmo…
bom galera tem muito mais pra falar sobre transações só arranhamos o conteudo, mas com isso já vamos evitar muita dor de cabeça né…
T+

Marcio

It is recommended that you create implicit transactions using the TransactionScope class, so that the ambient transaction context is automatically managed for you. You should also use the TransactionScope and DependentTransaction class for applications that require the use of the same transaction across multiple function calls or multiple thread calls. For more information on this model, see the Implementing an Implicit Transaction using Transaction Scope topic. For more information on writing a transactional application, see Writing a Transactional Application.

The top-most transaction scope is referred to as the root scope.

The TransactionScope class provides several overloaded constructors that accept an enumeration of the type TransactionScopeOption, which defines the transactional behavior of the scope.

A TransactionScope object has three options:

• Join the ambient transaction, or create a new one if one does not exist.
• Be a new root scope, that is, start a new transaction and have that transaction be the new ambient transaction inside its own scope.
• Not take part in a transaction at all. There is no ambient transaction as a result.

If the scope is instantiated with Required, and an ambient transaction is present, the scope joins that transaction. If, on the other hand, there is no ambient transaction, then the scope creates a new transaction, and become the root scope. This is the default value. When Required is used, the code inside the scope does not need to behave differently whether it is the root or just joining the ambient transaction. It should operate identically in both cases.

If the scope is instantiated with RequiresNew, it is always the root scope. It starts a new transaction, and its transaction becomes the new ambient transaction inside the scope.

If the scope is instantiated with Suppress, it never takes part in a transaction, regardless of whether an ambient transaction is present. A scope instantiated with this value always have null as its ambient transaction.

The above options are summarized in the following table.

When a TransactionScope object joins an existing ambient transaction, disposing of the scope object may not end the transaction, unless the scope aborts the transaction. If the ambient transaction was created by a root scope, only when the root scope is disposed of, does Commit get called on the transaction. If the transaction was created manually, the transaction ends when it is either aborted, or committed by its creator.

Although the default and most commonly used value of TransactionScopeOption is Required, each of the other values has its unique purpose.

Suppress is useful when you want to preserve the operations performed by the code section, and do not want to abort the ambient transaction if the operations fail. For example, when you want to perform logging or audit operations, or when you want to publish events to subscribers regardless of whether your ambient transaction commits or aborts. This value allows you to have a non-transactional code section inside a transaction scope.

Setting the TransactionScope isolation level

Interop with COM+

TransactionScope Class (System.Transactions).

The System.Transactions namespace can make the management of transactions quick and easy without the need to inherit from a ServicedComponent. One of the greatest features of the LightweightTransaction object is that it can determine if it needs to promote itself to a distributed transaction. The lightweight transactions are also a faster alternative to using the DTC for local transactions.

Late last year Congress passed a law aimed at softening the impact of the steep downturns in both the economy and financial markets. Among other things, the Worker, Retiree, and Employer Recovery Act [WRERA] allows anyone who must ordinarily take a ?required minimum distribution? [RMD] from a retirement plan or IRA to skip it this year. The goal is to give their account time to recover from the drubbing it took in ?08.

Those affected include retirees who are age 70½ or older as well as individuals who inherited someone else?s retirement account.

Unfortunately, amid all of the year-end holiday hoopla, a lot of folks never got the message. By the time they did, it was too late: they had already taken their withdrawal. Others, who have the money sent to them automatically, never thought to turn it ?off.?

Bending the Rules? for ?09

The problem is, the tax code specifically says that required minimum distributions can never be ?rolled over,? that is, re-deposited into a retirement account- either the same or a different one. Moreover, according to a different regulation that covers amounts that are eligible to be rolled over, you only have 60 days to accomplish this. Those who took retirement plan withdrawals and later found out they could have skipped this year (and this year only), figured they were out of luck.

Now the IRS has granted relief: a unique opportunity for an individual to roll the RMD amount back into their retirement account. This is available even if you received your withdrawal more than 60 days ago. In fact, it applies to an RMD taken [[[ any time ]]] this year.

Unfortunately, it doesn?t help everyone. And, there?s an additional wrinkle if the money came out of an IRA.

Doin? the RMD Roll-Back

The largest group of individuals able to take advantage of this are seniors who, as previously mentioned, are at least 70½- the age at which you must generally begin withdrawals from your own retirement accounts.(1)

If you fall into this category, your RMD amount can be re-deposited into the 401(k), 403(b), IRA or other retirement account it came from. If your company plan doesn?t accommodate this, then you can roll the money into an IRA.

This privilege also extends to spouses who are taking RMDs from a retirement account that was owned by their deceased husband/wife.

Notice that the maximum you can roll back into the retirement account is the amount you would have had to withdraw if required minimum distributions had not been suspended this year. For example, if your 2009 RMD would have been $12,000, and you withdrew $20,000 from your 401(k) account, only $12,000 can be re-deposited.

Rollovers Limited for Some Accounts

While Congress suspended required minimum distributions for this year, it didn?t change other regulations that affect retirement plans. As a result, these still apply. For instance, CPA Barry Picker with the firm Picker and Auerbach in Brooklyn, NY, explains that ?the law says IRA holders can only do one rollover per [calendar] year.?

This isn?t an issue if you take your annual RMD in a single check. But if you have it broken down into monthly or quarterly amounts Picker says ?you could roll only one of those checks back? into your IRA.

For instance, say you have instructed your IRA custodian to divide your annual RMD of $12,000 into 12 equal monthly payments. So far this year you?ve received 10 of them. Because of the one-rollover-per-year rule, you can only roll $1,000 back into your IRA.

On the other hand, the one-rollover?per-year limit does not apply to other types of retirement accounts. ?If you?re taking monthly payments from your company plan, normally these are not [ever] eligible to roll over,? says Picker. ?But this year you can .? Plus, you can roll over all of them, up to your RMD amount.

Suppose that in the previous example you were receiving your RMD in the form of monthly checks from your 403(b) plan (instead of an IRA). In this case, the entire amount you have received so far this year- $10,000- can be rolled back into the plan or an IRA.

Rollover Deadline

Everyone seems to have their own reasons for when they like to receive their annual required distributions. For some, it?s early in the year. Others want periodic checks. Typically, those who don?t need the money wait as long as possible and take their RMD at the end of the year. Still others, such as my mother-in-law, use their RMD as a surrogate ?Christmas club? account, and schedule it for mid-to-late November- just in time for holiday shopping.

If you already took a 2009 required minimum distribution and would like to re-deposit the money into your retirement account don?t dilly-dally. Contact your retirement plan administrator or IRA custodian and find out what?s required. You have until November 30th or as long as 60 days from the date you received the money- whichever is later - to return the funds to a retirement account.

If your RMD is scheduled to automatically be paid to you late in the year, don?t wait until you get the check and then figure you?ve got two months to roll it back. Things happen. Such as, the market takes off and you lose the full benefit because some of the mutual fund shares in your IRA had to be liquidated to cover your withdrawal. Or, you forget to do the rollover. Or, you end up in the hospital and miss the 60-day window.

CPA Bob Keebler of Baker Tilly in Green Bay, Wisconsin, says you?d ?be better off just to not take the money. It would make it easier.? Bottom line: if you don?t need the cash, contact your plan administrator or IRA custodian and cancel this year?s RMD before it can be automatically sent to you.

No Rollover For?

If you inherited the retirement account of someone who died last year or earlier and that individual was not your wife or husband, you, too, have the option of skipping this year?s required distribution. (Regardless of age, a non-spouse beneficiary of a retirement account must start RMDs by December 31st of the year after the account owner died, or empty the account no later than 5 years after the year of death.)

Let?s say you were the beneficiary of Uncle Henry?s IRA. In memory of Uncle Henry, each year you take your RMD on his birthday, which happened to be May 15th. Since you?re 42, working full-time, and really don?t need the money (or want pay income tax on it), you?d like to roll it back into Uncle Henry?s IRA.

No luck. While you could have skipped this year?s RMD, ?if you already took the distribution, you can?t put it back,? says Picker. ?Non-spouse beneficiaries never could and still can?t do a rollover.?

1. There is an exception for those who are 70½ or older and still working. Provided you do not own 5% or more of the company you?re working for, you can delay starting RMDs from your employer retirement plan until you retire.

Is a Roth Conversion Right for You?Don’t let summer’s laze reach your wallet

Antes de nada, un poco de teoría.

Una transacción en un Sistema de Gestión de Bases de Datos (SGBD), es un conjunto de órdenes que se ejecutan formando una unidad de trabajo, es decir, en forma indivisible o atómica.

Un SGBD se dice transaccional, si es capaz de mantener la integridad de los datos, haciendo que estas transacciones no puedan finalizar en un estado intermedio. Cuando por alguna causa el sistema debe cancelar la transacción, empieza a deshacer las órdenes ejecutadas hasta dejar la base de datos en su estado inicial (llamado punto de integridad), como si la orden de la transacción nunca se hubiese realizado.

SQL (Structured Query Language), provee los mecanismos para especificar que un conjunto de acciones deben constituir una transacción.

• BEGIN TRAN: Especifica que va a empezar una transacción.
• COMMIT TRAN: Le indica al motor que puede considerar la transacción completada con éxito.
• ROLLBACK TRAN: Indica que se ha alcanzado un fallo y que debe restablecer la base al punto de integridad.

Un ejemplo de transacción

Un ejemplo habitual de transacción es el traspaso de una cantidad de dinero entre cuentas bancarias. Normalmente se realiza mediante dos operaciones distintas, una en la que se decrementa el saldo de la cuenta origen y otra en la que incrementamos el saldo de la cuenta destino. Para garantizar la consistencia del sistema (es decir, para que no aparezca o desaparezca dinero), las dos operaciones deben ser atómicas, es decir, el sistema debe garantizar que, bajo cualquier circunstancia (incluso una caída del sistema), el resultado final es que, o bien se han realizado las dos operaciones, o bien no se ha realizado ninguna.

Ahora veamos unos ejemplos básicos con php.

BD de ejemplo:

create database transac DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

to usertr@localhost identified by 'pass123';

Es importante saber que las transacciones son soportadas solo para las tablas tipo innodb.

CÓDIGO PHP:

<?php
$SERVIDOR = "localhost";
$BASE_DATOS = "transac";
$USUARIO = "usertr";
$PASSWORD = "pass123";

?>

En el código anterior se ven 2 inserciones que se realizarán (COMMIT) si no ocurre ningún error en las dos, en caso contrario se regresarán sus valores anteriores (ROLLBACK).

CÓDIGO PHP usando la extensión mysqli:

<?php
$SERVIDOR = "localhost";
$BASE_DATOS = "transac";
$USUARIO = "usertr";
$PASSWORD = "pass123";

?>

CÓDIGO PHP usando la extensión PDO:

<?php
$DSN = 'mysql:dbname=transac;host=localhost';
$USUARIO = 'usertr';
$PASSWORD = 'pass123';

?>

CÓDIGO PHP usando PEAR DB:

<?php
require_once "DB.php";// incluir la clase de PEAR

?>

Live from VMworld 09, AppSense – the world leading User Environment Management solution provider – are extremely pleased to be awarded Gold in the Best Desktop Virtualization award for AppSense Environment Manager 8.0.

AppSense beat off strong competition from Liquidware Labs for their Desktop Virtualization Diagnostics tool, Stratusphere, and Workspace Virtualization vendor Virtual Computer Inc. for their NxTop product.

Like most that witness the capabilities of AppSense, the VMworld judges said “AppSense rocked our boat… It offers the most complete user environment management system out there.”  This comes as a further endorsement (following the recent announcement from Citrix) on the importance of a true UEM solution to enable enterprise adoption of VDI at lowest possible cost over and above basic in-built profile management technologies.

AppSense Environment Manager enables IT to deliver fully personalized virtual desktops from just a single set of OS and Application images, enabling scalable user adoption.  UEM allows organizations to implement virtual desktops at much lower TCO than using Profile Management alone.  “UEM addresses not just personal settings and profile data, but also the initial configuration of a desktop, including applying user installed applications, providing a ‘follow-me’ personality with cross operating system platform support, as well as enterprise-scalability and end-to-end visibility. Personalization settings can be managed across multiple operating systems, desktop delivery mechanisms and on virtual, physical and offline devices.” explains Pete Rawlinson, VP of Marketing for AppSense.

Oliver Sills, Senior Product Manager for AppSense Environment Manager said, “As you can imagine, we are delighted to win such a coveted award at this prestigious event.  We are continually working with our customers and partners to develop the solution and I would like to dedicate this award to our strong and committed development teams who have worked tirelessly to produce such a great product.”

Looking ahead, AppSense will continue to work with customers to enable some of the largest VDI deployments in the world, along with the development of the UEM solution set… with some extremely exciting product developments in the pipeline…

A list of the winners from the other categories can be found here

Further to my blog post, the official AppSense Press Release on winning this award can be found here

Jon Wallace, Senior Solution Architect and Head of US System Engineers

Sumit Dhawan over in the Citrix XenDeskop group has posted a very interesting article in the run up to VMworld 09.  I’m also hearing some interesting rumors about activity in user personalization space.  Sumit makes some very important points….which are all based on actual customer implementations. 

I’m also over in San Francisco attending VMworld this week and no doubt will hear about lots of upcoming companies and technologies, aiming to address the challenges of virtualized desktop management.  It’s great we have so many brains fixed on these issues now, but remember it’s all about what can actually be implemented in a customer environment.  We have to be pragmatic.  Through working with a substantial stable of customers, we know there is a right way to address the challenges of user personalization in desktop estates, and agree with the points Sumit makes in his blog.  Looking forward to more dialog on this!

Pete Rawlinson
VP WW Marketing, AppSense

Here is a quick excerpt from Sumit’s blog post along with link:

‘On the run up to VMworld 2009, there seems to be an increasing amount of activity on the subject of user personalization in VDI.  Even Gartner has written about dynamic workspace, which has user personalization as a key element of the stack. What does this mean?  What is user personalization all about? And, where does it need to be? Let’s take a closer look…….’

The full post can be found here.

This is the fourth installment in a series of posts about the new features and options in AppSense Version 8 Service Pack 2.  (If you have not yet downloaded this latest release, you can read more info and download it from here )

AppSense Environment Manager 8.0 Service Pack 2 introduces the ability to manipulate file settings from within the Personalization Analysis dialog for a selected user’s application.

Files can now be inserted, edited and removed.

The “View Application File List” has been improved to allow:

• Existing files to be exported from the cache
• New files to be imported into the cache
• Existing files to be deleted from the cache
• Existing files to be opened for editing

This can be seen in the screenshot below:

View File List

P:S
As this is an ever growing blog topic, the previous posts on the other new features we have detailed can be found below:

NEW FEATURE No. 1 – AppSense Environment Manager 8.0 Service Pack 2 – Run As

NEW FEATURE No. 2 – AppSense Environment Manager 8.0 Service Pack 2 – Connect As

NEW FEATURE No. 3 – AppSense Environment Manager 8.0 Service Pack 2 – Improved compression and data handling protocol

NEW FEATURE No. 4 – AppSense Environment Manager 8.0 Service Pack 2 – Manipulation of files in Personalization Analysis

NEW FEATURE No. 5 – AppSense Environment Manager 8.0 Service Pack 2 – Run Once

NEW FEATURE No. 6 – AppSense Environment Manager 8.0 Service Pack 2 – Group SID Refresh

NEW FEATURE No. 7 – AppSense Environment Manager 8.0 Service Pack 2 – Trigger Action Time Audit Event

NEW FEATURE No. 8 – AppSense Environment Manager 8.0 Service Pack 2 – Stop If Fails

NEW FEATURE No. 9 – AppSense Environment Manager 8.0 Service Pack 2 – New Application Categories in the User Interface

NEW FEATURE No. 10 – AppSense Environment Manager 8.0 Service Pack 2 – Refresh

NEW FEATURE No. 11 – AppSense Environment Manager 8.0 Service Pack 2 – Registry Hive Exclusions

This is the third installment in a series of posts about the new features and options in AppSense Version 8 Service Pack 2.  (If you have not yet downloaded this latest release, you can read more info and download it from here )

AppSense Environment Manager 8.0 Service Pack 2 introduces a new protocol for transferring data between the endpoint device and the server database which holds all the user personalization settings.

The change means that the Personalization Server now benefits as it has to do a lot less processing in order to insert or extract the required data from the database, and can therefore support a lot more users and even faster response times.

Part of this change is to store the user’s personalization data in a compressed format in the database, which means the required database footprint is a lot smaller (in some cases by a factor of 10).

Internal performance tests yielded the following results:

• 87.5% increase in performance scalability between version 8.0 and 8.0 SP2.
• 45.0% increase in performance scalability between version 8.0 SP1 and 8.0 SP2.

Note: On upgrade to Service Pack 2, User Personalization data is in the old protocol format. This data is upgraded to the new format, in the database, on demand as applications are used and such, will incur a small performance hit on first launch. However, once all endpoints are upgraded to Service Pack 2 and all data in the database has been upgraded, the performance of User Personalization will be much higher than previous releases and scalability will be dramatically improved.

As always, if you have any questions or require any further information, please do get in touch.

P:S
As this is an ever growing blog topic, the previous posts on the other new features we have detailed can be found below:

NEW FEATURE No. 1 – AppSense Environment Manager 8.0 Service Pack 2 – Run As

NEW FEATURE No. 2 – AppSense Environment Manager 8.0 Service Pack 2 – Connect As

NEW FEATURE No. 3 – AppSense Environment Manager 8.0 Service Pack 2 – Improved compression and data handling protocol

NEW FEATURE No. 4 – AppSense Environment Manager 8.0 Service Pack 2 – Manipulation of files in Personalization Analysis

NEW FEATURE No. 5 – AppSense Environment Manager 8.0 Service Pack 2 – Run Once

NEW FEATURE No. 6 – AppSense Environment Manager 8.0 Service Pack 2 – Group SID Refresh

NEW FEATURE No. 7 – AppSense Environment Manager 8.0 Service Pack 2 – Trigger Action Time Audit Event

NEW FEATURE No. 8 – AppSense Environment Manager 8.0 Service Pack 2 – Stop If Fails

NEW FEATURE No. 9 – AppSense Environment Manager 8.0 Service Pack 2 – New Application Categories in the User Interface

NEW FEATURE No. 10 – AppSense Environment Manager 8.0 Service Pack 2 – Refresh

NEW FEATURE No. 11 – AppSense Environment Manager 8.0 Service Pack 2 – Registry Hive Exclusions

Finally, after three days, Ichiraku is back again, only with a minor caveat. Full public release from the administrators:

Hello everyone,

It’s a big day for us as Ichiraku is finally back after being down for three days since August 7!

We are still looking for the probable cause of the problem and we are currently engaged in a manhunt, of sorts, to pinpoint the culprit. While the initial diagnosis was a hack case, we figured that the problem was too selective to have been due to a single person with malicious intent. This is due to Ichiraku’s SMF files removed from the server, while the rest were not.

We worked around this problem by reinstalling SMF and calling back a server backup made on 9:00am (GMT +8) of August 5th thus having a roll-back. All posts made on the day of August 6 will be lost, but I’d daresay this is better than restarting and rebooting all over again. We have also returned the Ichiraku Mail service (www.mail.ichiraku.org) last night, and assigned a new URL to Ichiraku DEV (http://support.ichiraku.org), although, alternatively, you can still access our support blog at its old address.

For the meantime, I and akee ask everyone to be very vigilant. Since this may not be the last time we see this – I will not give you false guarantees, because it MIGHT, and I want everyone to be with us as we fight these glitches or errors – please tell us as soon as you can. Meanwhile, I and your faithful staff will do we all we can to further safeguard our community from pernicious attacks, human or otherwise, in the future.

Thank you everyone for your continued support!
The Ichiraku Admin Team

—-

Enjoy everyone! And a little thank-you note wouldn’t hurt at all.

As a leading user environment management vendor, AppSense are in a unique position in that we have been involved many VDI projects and rollouts, of which the majority vary in architecture, technology and requirements.  One thing that does however remain the same between such projects is that of the requirement for user personalization management.

For many years the roaming profile provided user personalization in SBC environments, however as VDI deployments become more and more complex, with varying methods of desktop and applications delivery, along with multiple desktop operating systems and subsequently, profile versions, the roaming profile is no longer able to provide the user with their required settings in such (complex?) scenarios.

Furthermore, these desktops must now be constructed and configured based on the context of the user and/or connecting device.  i.e. mapping specific printers local to the user and device dependent on the location of the user logging on, or applying security policies to hide or remove access to network drives, folders, data and functionality such as copy and paste or print, again, based on the location of the user.  Whereby the desktop delivered to a user when connected locally inside the corporate LAN is different to that of the desktop delivered to the same user when connecting remotely from outside of the LAN.

One more point to consider is that of enabling the user to freely roam between the server hosted or provisioned virtual desktop, and the users local desktop device such as their PC or roaming laptop.  How do you as IT enable user settings to automically follow the user between different platforms?

AppSense Environment Manager was designed from the ground-up with functionality to accommodate the above requirements, making it, or, other user environment management solutions essential to the mass adoption of VDI on an enterprise scale.  In essence, AppSense provides the ability to encompass multiple delivery technologies and OS platforms by allowing the user to roam between the paradigms without any noticeable change to their desktop or user experience, enabling IT and the organization to benefit from flexibility, agility and lower TCO.  I do at this point want to highlight that this is different to the personalization management provided by the leading VDI vendors (Citrix, Microsoft, VMware etc), as their in-built functionality is typically designed for their delivery platform, not each other’s.   In essence, further to the advanced personalization and simplification of desktop management, AppSense also enables an organization to use combinations of both existing technologies, and (potentially) more importantly, any future VDI delivery technologies and vendors.
 
I have just found a very nice blog covering the functionality of not only AppSense Environment Manager, but also the base technology inherent within the leading VDI service providers – Citrix, VMware and Microsoft.  Hopefully from this blog post, and the information over at GenerationV, you will see how AppSense bridges the gap between the roaming user and a dynamic, flexible VDI model..

For more information on this, the GenerationV Profile Management blog can be found here

I am excited about writing this one, the much awaited 2009 AppSense Technical University is soon upon us! It will take place in October and November!!  Following on from our previous events, there are some exciting new developments at AppSense that we would like to share with you; amongst other topics:

• User Introduced Applications (UIA) Technology – do we need, and how do we enable, users to install applications into non-persistent VDI sessions, and have the applications (and settings and preferences) remain available in the next non persistent vdi session?!
• AppSense Management Suite Version 8.1 Product RoadMap
• ‘Policy & Personalization’ best practices across virtual and multi OS platform environments

Why attend the AppSense Technical University?

The AppSense University is a ‘free of charge’ event to our AppSense Certified Solution Partners, and is a great chance to meet up with the AppSense Technical teams, as well as your peers from within the community. As a valued member of our Certified Solutions Partner program, you are invited to this comprehensive technical update and networking event.

The 2 day event will include in-depth, hands on training designed to enable you to provide consultancy services and implement the AppSense Management Suite for prospects and customers.

Register for further information

As always, AppSense is hosting several Technical University events in locations around the globe. If you are interested in attending an AppSense Technical University, click on the country or region most relevant to you and we will keep you informed of the event details:

United States, November 2009 

United Kingdom, October 2009

Norway, November 2009

DACH Region, November 2009

BeNeLux, November 2009

Australia, October/November 2009

We look forward to seeing you there!

Best Regards,

The AppSense Technical University Team.

Website: http://www.appsense.com
Email: university@appsense.com
Telephone: +44 (0)1928 793 444

SUDDEN ROLLBACK on OIL PRICES COULD BE DECEIVING
Let us not be complacent with the recent fall. Along with conservation, U.S. has to totally reroute its oil resources from non-muslim allies.
http://www.associatedcontent.comarticle/951765/sudden_rollback_on_oil_prices_could.html