I resolved my issue on my own. After doing this I reread the question and with the knowledge I now have I as a different user I would have known exactly what I needed and would have answered that user with about 3 sentences
Reboot your PC after setting up the Azure database
Review the table schema of your access database and make any name changes that might be a conflict with sql server
Get SSMA which is the migration tool for Access - Must have
4 - follow the instructions - so easy
I stand by the question. Sometimes we tend to either over engineer a question or answer when the most obvious is the simplest
Problem - set up db on azure now I can't figure out how to migrate an access db because that is not an option like other db's in the list.
Answer - Oh I had the problem when I first signed up with Azure - you need to do the following
(See above)
First of all I am not stupid by any means and have been developing software since 1992, but the interface for this whole Azure thing is just horrible and the overhead to do anything is so extreme. With that said I created and azure database service using my company ID Created the server and database Went to the migration services. I am migrating a mission critical access accdb backend to this azure site to see how it performs At first I thought I could use SSMS locally to see the database but I could not. So, knowing that there is no more "upsizing" I figured the site would walk me through. I answered the questions ( none about the source) but when I try to save or continue the buttons are disabled I did install the hybrid worker as instructed as well I do not understand where why there cant just be an option that says upload an acees database and it go from there. lol or why I can't see it from SSMS on my machine
Use the tool for the job: Microsoft SQL Server Migration Assistant 8.12 for Access.
Related
I have three laptops and one desktop joined to Active Directory hosted on Azure. I am trying to join a new workstation to Azure AD using the email address of a person who has a laptop connected to Azure.
Here are my steps.
Connect to Work or School.
Connect.
Join this device to Azure Active Directory.
Enter user's email address and password.
I receive the following error when trying:
"Looks like the MDM Terms of Use endpoint is not correctly configured."
I've checked whether "Users may join devices to Azure AD" is set to ALL. (It is.)
The number of devices per user is set to 20.
Where do I go the portal to resolve the issue?
I know that this is an old question but I'm hoping it can help others avoid hours or days trying to figure out. Even Microsoft couldn't figure this one out which is sad. Their documentation actually even contradicts the solution.
During your domain setup, there are two CNAME records that you are instructed to create: EnterpriseEnrollment and EnterpriseRegistration. What they don't tell you is that this is only used if you are using the free MDM for Office 365 solution. If you are using, or switch to a license of Active Directory Premium and/or Intune, you MUST remove these CNAME records in order to allow your devices to register. It worked for me instantly upon removing the records on Cloudflare, though there may be a delay depending on who you use for DNS management.
I hope this helps anyone encountering this issue. Microsoft really needs to work on the detail of their error messages.
I see you got a couple answers on Reddit - but here goes,
Firstly, make sure you have one of the more advanced AAD services (such as P2) not the free one which has almost nothing whatsoever to do with AD.
AAD seems to "propagate" slowly ala Y2K Domains. I get this error often and there might be more than 1 root cause (thanks to the cryptic message in the first place).
Similar symptoms:
MDM TOU error when activating brand-new PC
Vague error regarding connectivity when setting PIN
"Successfully" connecting to work but no listing in Intune
For all of the above, I find simply waiting about 24 hours before trying again often helps as the newly created user/device/passport/hello propagates through Microsofts complex cloud ID servers.
I have had it fail with your message and then retry 30-seconds later and it works (forever from then-on) and I have had devices which "join the workplace successfully" but not show up in Intune/AAD for almost 48 hours!
I develop software in a multi-programmer source controlled world (TFS). Moreover, I have multiple environments (i.e. individual desktop developer machines, QA and production in the Azure cloud). The problem is, I'm unsure as to the best way to use different database connection strings for each environment. I realize that I can manually update the web.config for the Server project but that causes a clash when check-in occurs. This is a pretty critical issue for our team, so any help in this regard would be greatly appreciated. Thanks....
We are considering to build a webapplication and rely on Azure. The main idea behind this application is that users are able to work together on specific tasks in the cloud. I'd love to go for the concept of instant releasing where users are not bothered with downtime but I have no idea how I can achieve this (if possible at all). Lets say 10.000 users are currently working on this webapplication, and I release software with database updates.
What happens when I publish a new release of my software into Azure?
What will happen to the brilliant work in progress of my poor users?
Should I bring the site down first before I publish a new release?
Can I "just release" and let users enjoy the "new" world as soon as they request a new page?
I am surprised that I can't find any information about releasing strategies in Azure, am I looking in the wrong places?
Windows Azure is a great platform with many different features which can simplify lots of software management tasks. However, bear in mind that no matter how great platform you use, your application depends on proper system architecture and code quality - well written application will work perfectly fine; poorly written application will fail. So do not expect that Azure will solve all your issues (but it may help with many).
What happens when I publish a new release of my software into Azure?
Windows Azure Cloud Services has a concept of Production and Staging deployments. New code deployment goes to staging first. Then you can do a quick QA over there (sometimes "warm up" the application to make sure it has all caches populated - but that depends on application design) and perform "Swap" - your staging deployment becomes production and production deployment becomes staging. That gives you ability to perform "rollback" in case of any issues with the new code. Swap operation is relatively fast as it is mostly internal DNS switch.
What will happen to the brilliant work in progress of my poor users?
It is always good idea to perform code deployments during the lowest site load (night time). Sometimes it is not possible e.g. if your application is used by global organization. Then you should use "the lowest" activity time.
In order to protect users you could implement solutions such as "automatic draft save" which happens every X minutes. But if your application is designed to work with cloud systems, users should not see any functionality failure during new code release.
Should I bring the site down first before I publish a new release?
That depends on architecture of your application. If the application is very well designed then you should not need to do that. Windows Azure application I work with has new code release once a month and we never had to bring the site down since the beginning (for last two years).
I hope that will give you better understanding of Azure Cloud Services.
Yes you can.
I suggest you create one of the visual stdio template applications and take a look at the "staging" and "production" environments located directly when you click your azure site in portal manager.
Say for example the users work on the "production" environment which is connected to Sqlserver1. You publish your new release to "staging" which is also connected to Sqlserver1. Then you just switch the two using the swap and staging becomes the "production" environment.
I'm not sure what happens to their work if they have something stored in sessions or server caches. Guess they will be lost. But client side stuff will work seamlessly.
"Should I bring the site down first before I publish a new release?"
I would bring up a warning (if the users work conissts of session stuff and so forth) saying brief downtime in 5 minutes and then after the swith telling everyone it is over.
What I want to build is an application that sits online and it's used by different groups that each have their own intranet. Now, because of a stupid security policy the data can't sit outside the intranet. How would you go about building an app that it's still online, so you can push updates to everyone at once, but has a DB on each intranet's server?
My initial plan is to use Node.js and MongoDB.
If your db really has to be onsite, and your app really has to be offsite, then probably your only option is to set up a secure connection from your app, to the onsite db, and pretend as if its hosted locally to the app. This may/may not violate the security policies. You could in theory lock it down pretty well, with a vpn between the two networks. But this is not for the faint of heart, performance will suffer, and it does have security issues. It also means a bit of work for every site.
If the only reason you're wanting it to be "online" is for pushing updates as you stated, then you'll do better installing the app on-premise, and getting it to poll into a central server for notifications about new versions, download updates to itself, and install them automatically. Once you've created this, a new installation requires no new work.
I'm facing a similar problem right now, so here's my take on it, not really mongo or node specifc.
Put a db and a simple restful server on each of client's intranets. Servers can be exactly the same.
Put a routing facade accesible from internet that redirects requests to apropriate server based on url, ie: http://facade/server/resource becomes a request to http://server/resouce.
Configure the facade so that a requests to http://facade/resource go to each server, retrieve results and return all of them in some aggregated form.
Obviously there are more details to take into account, like permissions (can everybody publish to each server? if not, who can?), but the general idea is there.
Does anyone have recommendations on the best way to set up development and testing environments for Microsoft CRM 2011 On Demand?
The recommendations I have seen so far include:
Paying for another account with only one user
Creating a VM
Going with a partner hosted environment
You will need to be a little more specific. What's wrong with the 3 you have listed? Is it cost, it is the time to configure?
That being said, what I do is sign up for the free 30 day trial.
First, sign up for a new Windows Live account.
Second, click here to sign up for the 30 day account.
Third, I always write down the login & url because I always forget them.
I'll have anywhere from 1 - 5 of these running at once.
The main benefit is the control this gives me. Since you can't access the SQL server directly with On Demand, it forces you to make your configurations & customizations the correct way.
Your other option is to setup a VM environment and create a new instance every time you need a clean setup. This is not my preferred option since you need good hardware to run the environment (otherwise the performance penalty is huge)