When planning a cloud migration, don’t forget to plan ahead for IP address changes that could affect your workloads and the way they interact with internal and external network traffic.
Cloud providers and data centers have a limited pool of IP addresses that they own, and they often re-use previously assigned IPs in order to maximize them. You can’t simply move your existing IP addresses along with your services. Rather, you’ll receive a dynamically assigned internal and external IP address.
To complicate matters, you could lose those dynamically assigned IPs if you stop your cloud instance (but usually only if you stop and deallocate the VM resources — most providers will keep your IP assigned to you if your machine is paused/stopped but still reserved within the overall resource pool). Luckily, there are a few ways to keep IPs relatively static in the cloud.
Well, maybe not quite everything.
You still need a strong — and long — password. And you still want unique passwords for each of your credentials.
But you don’t need to add any special characters or numbers, at least if you don’t want to. And you don’t need to change your password every month, or every week, or every day (even if it feels like the IT department is making you change it that often).
Here’s why experts are no longer recommending passwords like k1TTyc@7z or @ppl3Be3s — and what they say you should be using instead.
As we prepare to celebrate our 10th anniversary, Green House Data continues to grow and add new facilities, office locations, product offerings, and services. Our customer roll has grown alongside us as existing clients embrace those new offerings and new markets bring new opportunity.
We aren’t the only ones recognizing that growth — CRN, part of IT media group The Channel Company, recently named Green House Data number 32 on its list of the Fast Growth 150.
The list is CRN’s annual ranking of North America-based technology integrators, solution providers, and IT consultants with gross sales of at least $1 million that have experienced significant economic growth over the past two years.
Moving to Office 365? The user experience is bound to shift, with one of the biggest changes coming to the login process.
Each workstation might previously have had Office software installed locally, so once users signed in, they were free to launch and work on Word or answer e-mails in Outlook. With Office 365, you’ll have to configure user identity settings in a specific way to replicate this — or you can go the cloud-only route and have them sign-in again online in order to access these programs.
Here are some of the factors you’ll have to consider when setting up user identity management in Office 365.
While designing a new application may be the hot development path right now, enterprise organizations have a multitude of legacy applications that should not be ignored when undertaking a cloud initiative.
If you’re preparing to migrate some or all of your applications to a cloud environment, you’ll need to examine them and determine which of these four categories they fall under. With careful planning and perhaps some investment in development, your applications will work just as well in the cloud as they did on-premise.