Cache

We don't have any link in place at the moment. I have a plan to either link via some sort of unique ID or simply put the network username into SIMS in a UDF, however that is far from fruition at the moment.

Yes, when the sync next occurs all those users will move to the recycle bin (can't remember whether it's called the recycle bin or not but you get what I mean)

No your right, it confused me at first. Delete the msol account name and enter the administrator account details for your domain and then you can filter on the ou.

I followed this guide for the OU level filtering and it worked perfectly: Installing and Configure DirSync with OU level filtering for Office365 - Denotation - Site Home - MSDN Blogs In regards to the onmicrosoft domain. For your already synced users, you will need to either bulk edit the users through the Office 365 Portal or run the Powershell command above with some sort of scripting to do all your users. If you want DirSync to set any new users up with your domain name automatically, you will need to configure it as an additional UPN within your Active Directory. (I haven't done this, I'm still on the manual activate and alter UPN stage in the portal and is working quite well so far, touch wood!)

Spotted that soon after I posted. Nearly everything is listed in the Bypass proxy exceptions, I just need to make sure it's all listed and then I'm away. Can't tell you how much this has made me day (shows what sort of time I'm having at the moment!)

OMG! Your a genius! Now why the hell does that make it work? I can't remember why I have it ticked now (just assumed you needed it), what am I going to lose by unticking it?

Not likely to be a possibility for us unless things change drastically in the next month I still don't get the fact that it is fine working with a pac file though, regardless of the proxy the pac file specifies. Maybe I'm getting hung up on it, but it's really bugging me now

I do quite like the solution of DirSync with Password Sync, it's removed a lot of the "I can't remember my password because it's different from the computer" arguements we used to have and staff are being a bit more receptive to it. It's also the setup we dived straight in with on filtered OU's after the initial testing was complete and was very easy to go with. The only thing some users don't particularly like is typing the whole email address in rather then just their username, however that is the least of my worries and not a fantastic reason to look at the SSO/ADFS route at the moment.

Frustrating indeed. When you say Link2ICT changed it to an IP format, do you mean using the IP address in the specify a proxy server rather then the DNS name or did they do some other magic? Just to prove the point, changing the proxy while Outlook is open still has a performance impact once Outlook recognises the change which is really annoying as I think I know the cause but don't know the problem or solution other then going back to a PAC file

This is what confused me, just remembered cumbria have their own Pac file too. No matter which pac file I use, the CLEO/One Connect or Cumbria (Can't make my smoothwall one work for some reason, but that's me not getting smoothwall somewhere along the line) it works instantly (nearly, not faultless) everytime. The issue only rears it's head if I tell it to use the proxy directly. If it was firewall related, surely it would still occur using the pac file? I wonder if it is an Outlook issue.... Edit: Fixed my Smoothwall pac, it works instantly as well when configured to use that...

Who fancies helping me with this one then...... This happens across the site, however it has only just clicked into place the potential issue which has been plaguing me. Several users use Outlook, including myself, to access Office 365 which isn't unreasonable. Several of us, including myself, occaisionally have long delays when logging into our Mailbox, looking at the connection status in Outlook, it is taking a long time to connect to the severs. The cause, for whatever reason, is the proxy configuration which makes no sense to me at all. The default setup currently for staff is to use an Autoconfiguration script in order to go through a specific proxy to grant access to Youtube. If this is used then Outlook works without issue most of the time, connecting and opening quickly. If you alter the setup not to use the Autoconfiguration script, which we need to do sometimes because the proxy we use does something weird to some websites requiring logins meaning they don't work, and set it to use a specific proxy then all of a sudden Outlook takes an age to connect to Office 365. This is regardless of the specific proxy server you configure it to use, even if it's configured to use the same one the autoconfig script points to (CLEO NED), Smoothwall or straight out to the Cumbria one. Any hints as to what the heck is going?

Ok, that means that the agent, although installed, didn't register correctly within Solus3. What I would do is remove the computer from Solus3 that doesn't have an agent version and uninstall the agent on the Door Control server. You mention you can ping the IP address, can you ping the computer name for one of your desktop computers (Solus3 works off the computer name, looking that up in DNS to get the IP Address). The fact that all your agents are appearing offline and that the Door Control Server didn't register the manual agent install suggests something isn't right somewhere. Are you sure the required firewall ports are open on both the server and clients? Regarding the Solus3 Service not starting on some machines, I've had this a couple of times, I've got one which I still haven't fixed, the majority though I've managed to manually reinstall the agent on the computer by opening a command prompt and changing the directory to the exported agent installer. From there manually running the command msiexec /lv* c:\solus3install.log /i SOLUS3AgentInstaller_x86.msi and using the values from the .bat file to fill in the prompts or just repairing the installation has resolved most of them. I've only needed to do this since the 3.6.92 version was released, do you know which version you are running?

Not part of the domain, but must be connected to the network in order to have SIMS on. What you need to do for this is on your Solus3 Console is export the Agent Installer which is listed under the System Settings screen. You can then take this and run the Solus3AgentInstaller.bat file on your Door control server which will install the Solus3 agent and register it in Solus 3. If you then go back to Solus3 Agents and then your Deployment Environment, find SIMS Workstation and Select a Computer, Add and from the left hand side choose Browse Agent Computers which should then list your Door Control machine in there.

Pleased it helped out (and it does seem odd that it is hidden so far down and off screen I agree, considering how useful it is!)

We've got this exact same problem. If you change the options so that it uses (from memory) hardware acceleration instead of software whichever way round it goes, it resolves it. I suspected, but haven't tested yet, that if I bought a newer graphics card with more up to date Windows 7 drivers rather then the integrated Intel graphics that might resolve the problem. It did function perfectly well in Windows XP however on the same machines. Don't know if that helps?

What do you want to do with the Student in this BTEC class once they've been removed? If you just want them to be removed and have a blank on the timetable, if you go into the Curriculum Assignment by Student Screen you can click on the lesson which you want and then search for the student. You can then scroll down to the timetable at the bottom, select the lesson that you want and then remove the membership for that lesson (I think, it's a couple of years since I've had to do it). It works the same way as the alternative curriculum, however we don't use that. What we do is Timetable clashes within Nova-T6, sned the timetable across, allocate the students to the group and then go and resolve the clash by removing them from one of the 2 lessons. It's a faff, but it still works for us.

Wonder if this will apply to Cumbria schools too?

I meant redeploying patches which have already been deployed once by Solus3 (sorry).

Sorry, misread your first post Phil, hopefully the next update can increase it's retries then. Thanks!

I can udnerstand the reason behind preventing a loop, however it is definitiely only running once per day for me: 2013-09-16 12:30:35.0174|Error|DsLog not open when attempting to write: 2013-09-16 12:30:35.0174|ds|Info|Deployment timeout (30 minutes) exceeded for agent sh-off-01.school.kirkbystephengrammar.local!|Execute() 2013-09-16 12:30:35.0174|Info|Agent sh-off-01.school.kirkbystephengrammar.local has responded 2013-09-16 12:30:35.0174|Debug|Pending|Pending deployment id 147 for sh-off-01.school.kirkbystephengrammar.local (7c33ab47-5761-4173-8449-c3ecd337cc9e) was not successful and will be queued again 2013-09-16 12:30:35.0344|Debug|Pending|Setting pending deployment 147 as INACTIVE for sh-off-01.school.kirkbystephengrammar.local (7c33ab47-5761-4173-8449-c3ecd337cc9e) 2013-09-16 12:30:35.0464|Debug|Pending|No pending deployments found for sh-off-01.school.kirkbystephengrammar.local (7c33ab47-5761-4173-8449-c3ecd337cc9e) 2013-09-16 12:39:40.4980|Info|Agent SH-OFF-01 was shut down. 2013-09-16 12:40:14.8574|Info|Agent SH-OFF-01 woke up. 2013-09-16 12:40:14.8804|Debug|Processing Agent notification for Agent guid 7c33ab47-5761-4173-8449-c3ecd337cc9e 2013-09-16 12:40:14.9274|Debug|Validating target version info received from agent 7c33ab47-5761-4173-8449-c3ecd337cc9e 2013-09-16 12:40:14.9274|Debug|Original number of target version info DTO's = 0. Distinct number of target version info DTO's = 0 2013-09-16 12:40:14.9274|Debug|Validated number of target version info DTO's = 0 2013-09-16 12:40:14.9274|Debug|Verifying target version info received from agent 7c33ab47-5761-4173-8449-c3ecd337cc9e 2013-09-16 12:40:14.9464|Debug|Pending|No pending deployments found for sh-off-01.school.kirkbystephengrammar.local (7c33ab47-5761-4173-8449-c3ecd337cc9e) *SNIP* 2013-09-16 19:42:35.8032|Info|Agent SH-OFF-01 woke up. 2013-09-16 19:42:35.8592|Debug|Processing Agent notification for Agent guid 7c33ab47-5761-4173-8449-c3ecd337cc9e 2013-09-16 19:42:35.9432|Debug|Validating target version info received from agent 7c33ab47-5761-4173-8449-c3ecd337cc9e 2013-09-16 19:42:35.9432|Debug|Original number of target version info DTO's = 0. Distinct number of target version info DTO's = 0 2013-09-16 19:42:35.9432|Debug|Validated number of target version info DTO's = 0 2013-09-16 19:42:35.9432|Debug|Verifying target version info received from agent 7c33ab47-5761-4173-8449-c3ecd337cc9e 2013-09-16 19:42:35.9672|Debug|Pending|No pending deployments found for sh-off-01.school.kirkbystephengrammar.local (7c33ab47-5761-4173-8449-c3ecd337cc9e) As it turns out, something had corrupted the Solus3 install, not sure what, but the packagedeployer just keeps crashing on the client. Eventually found out I can manually upgrade them using the the exported Solus3 Agent installer. Could well be because it's a Solus3 update and happy if it's something to do with my install, but just curious how many times it should reattempt before failing?

Do you find this works? I had to redeploy the btec exams patch this summer which is supposed to be an OnDemand patch I think (has [OD] in the patch name in Solus3) and Solus3 rather helpfully told me that the patch had already been deployed and wouldn't redeploy it no matter what I tried as there was no redeploy link next to it. Had to call up and ask for the patch to be emailed across and rerun it using dbupgrade. I wouldn't trust Solus3 to apply a SIMS upgrade while I wasn't there, one major bad experience and it's scarred me for life. I do schedule and leave to run early in the morning Solus3 and Discover updates. I do like the fact that now if a deployment time's out when a machine is offline, it will reschedule the deployment. I dislike the fact that it only tries the schedule once per day (which is useless because obviously I need to retry it ASAP).

Sorry, that's now beyond me, but you could be on the right lines. I would *guess* that if you create a forward lookup zone of adfs.school.sch.uk on your internal dns server and then create a blank host record and enter your internal ip address that might do it? But I'm really really not certain....

Now just hold on a second ... Not heard of sugar mice..... I'm happy to report, I recieved some some Angry Birds fruit pastilles with the bad piggie packaging

Well if it doesn't happen on a local account I guess it is something to do with your SSO setup (but that's beyond me). It might be worth downloading the new Microsoft Connectivity Analyzer from the Tools section of the Office 365 portal and see if that brings forth any issues? You'll need to install .net 4.5 before it will run however.

No, I'm quite happy with the actual onmicrosoft.com domain we've got (fits in perfectly with the school domain). When creating the user, dirsync gave it a [email protected], renaming it put it out of sync so it was [email protected] and still had [email protected]. I've now got it to have [email protected], [email protected] and [email protected] Sorry, I've probably not explained it all very well. Because it's dirsync'd I can't remove the [email protected].