Basic CMS with decent upgrade path
I am maintaining this website for a not-for-profit organisation (www.snjv.be) and currently it is running Drupal. However, upgrading can be a real hassle between major versions (I tried backing up the MySQL database from a Drupal 5 installation and re-importing it into a Drupal 6 install but no dice).
So I'm looking for a nice but not too complex CMS that provides decent upgrade paths. I'm no PHP or MySQL wizard, but I can get around with a bit of hacking (mainly PHP snippets).
If you need to know anything else, just ask.
.:B:. wrote:
MikeT wrote:
B wrote:Okay, I guess I should have mentioned: I don't like wordpress .
What puts you off Wordpress so much?
Mike
When I started setting stuff up, it had a bad reputation when it came to security. I don't know how that is now, but it's been in the news a few months ago - with a major security issue. So I'm not really comfortable with it.
That's a fair enough point and completely true even now. There is of course things like http://www.seoegghead.com/software/word … rewall.seo now but I won't try and convince you otherwise if you have a dislike of it!
Mike
Similar Messages
-
Upgrade Web Basics from with a CS6/CC subscription
I have a CS6/CC subscription.
I have a website created in Muse that is hosted on BC using the Web Basics plan that is included in the the subscription.
I am considering upgrading to one of the paid for web plans but I cannot find a way of doing this from within my existing subscription. I have just wasted 20 minutes on Abobe Chat with a man who clearly didn't know the answer either, hence my asking the same question here.
Please advise.
Thanks
GrahamHi Sidney and Alexandru
Thanks for your responses. However I am very surprised that the BC that provided as part of CS6/CC/Muse subscription is ring fenced from a BC subscription taken out seperately, there seems no business or technlogical logic for this.
At the very least I would like to be able to host email with BC for domains that I have used Muse to create websites for. And if I have clients who would like to use some of the more sophisticated elements of BC like eCommerce and Content Management then I would expect a seamless upgrade path within my current subscription.
I have a current issue with Cookeryclassics.com, I am finding it impossible to host email for this domain unless I either use Google Apps or apply for a seperate BC sub. I would rather do the latter if I could simply add a new service to my existing subscription.
Best
Graham -
SRM Addon Upgrade Path with ERP2005 ( ERP 6.0 )
We are on the verge of finalising the implementation of SRM5.0. If we
go on SRM 5.0 add-on path then what is the next upgrade path that is
available with ERP 6.0. We have looked at SAP notes 963000 and 853651
which clearly say that "SRM as add-on is only supported in the release
combination ERP 6.0 and SRM 5.0 and other release combinations are not
supported. Also future SRM release will not run as add-on on ERP 6.0".
We have also looked at other SAP notes 863532, 982871, 1012010, 1012231
for the same issue.
Can we get more details on the upgrade path for SRM add-on that will be available in
future release with ERP 6.0.Hi,
As you mentioned you have read in notes the SRM as an ADD-ON will no longer be supported by SAP, there are no plans for further and future integration of ERP and SRM directly, it is advisable to implement the SRM_SERVER on it's own and not as an add-on.
Regards,
Jason -
Is there an upgrade path from Logic Pro 9 to Logic Pro X?
I convinced a friend to purchase Logic Pro 9, not knowing version X was about to be released 3 weeks later. Even though upgrade path always crosses my mind prior to a software purchase, I was not worried - this was Apple. Now it's looking like there's not a built-in upgrade path at all (as there IS with just about every other software company I have bought from). Is this for real? This friend has version 9, and I have version X. So this friend learned everything there is to know about version 9, then I bought version X not even knowing we were out of synch on versions. We were hoping to work on songwriting together, but paying $200 again is out of the question. I notice that the file save under version X has extension .logicx, so is it even possible to exchange files?
my friend with Logic Pro 9 can send files to me but they cannot accept files created with Logic Pro X.
Which is exactly what i said earlier....
You can open Logic Pro 9 projects in LPX but not the other way around.
Apple wouldn't even give me a refund on Logic Pro X (purchased just 3 days ago), which is useless to me now.
There are no refunds from the App Store... That is what you agreed to when you purchased a license for LPX.
Your choice is simply for your friend to update to Logic Pro X or use the audio stem process I outlined earlier (Not something i would recommend doing for any period of time)... or spend even more money on purchasing two copies of a different DAW... and taking the time to learn them and spending time converting over what your friend has already created... and hope your friend hasn't been using the internal plugins found only in Logic Pro... otherwise you have even more work to do...
The reality is, the sensible solution is simply to upgrade LP9 to LPX for $200... (and think of it as the upgrade price even though you can buy the full version for the same amount but that really doesn't matter does it?) Less outlay, less time lost and less hassle, but as always the choice is yours...
I have never, EVER, encountered a software company that treated customers that way.
Then you haven't been in the computer business that long......
Seriously though, you haven't been treated that badly...
You bought LPX at a price that is basically a steal.... and your friend bought LP9 at the same 'deal' of a price.. compared to what Logic Pro used to cost ($1000)
You can 'upgrade' from LP9 to LPX for $200 which is much cheaper than it used to cost to upgrade from , say LP8 to LP9... and the same price as it cost to upgrade to LP9 via the App Storeprior to the release of LPX
The alternatives at this stage would cost you much more money......time.. and hassle..
The only things that truly frustrating is the timing of your friend's purchase of LP9... For that he has my sympathies but it happens... Some people who bought Logic Pro 9 within a month of Logic Pro X being released were given refunds on the LP9 purchase if they bought LPX... Your friend just left it way too late.... Apple has since stopped such refunds.... and you didn't do the research you should have done before you jumped in and bought LPX... Unfortunate but sadly true.
Again, you and your friend have my sympathies for whatever they are worth... but at least the obvious solution is still cheap compared to what the alternatives could cost you now and in the past! -
I bought a copy of A.W. 6.0.4, my iBook is completely X. I can not install the 6.0.4 and the updater will not recognize the install CD as being in the "correct" area.
Any ideas on how to make a upgrade path so I can get A.W. 6.0.4 to 6.2.9.
I do have a OS 8.6 computer but if I install 6.0.4 to upgrade I will be installing another copy of Apple works. I am stuck
Thanks
SueHello Susan,
Classic installs under OS X as if it were another program. Basically, classic mode runs just like any other program in OS X. It doesn't require you to remove OS X first.
So, it shouldn't be much of an inconvenience. I think it only takes a couple of minutes to run the installer (it's been a while since I installed it).
I can understand if you didn't want Classic on the machine, but it doesn't require anything fancy (no removal or changes to OS X) to install it.
Basically, if you install Classic under OS X, it just looks and behaves like any other OS X application.
To run classic, you just launch it, and then run any of the OS 9 applications you want. OS X then decides whether it is a classic mode program or OS X program and handles it accordingly. For all intents and purposes, it is pretty seamless.
Some people have classic mode configured to launch with the booting of OS X. Then, you can run OS 9 and OS X programs side by side, and not have to even think about classic mode. In that arrangement, you wouldn't even think about whether it was an OS 9 or OS X application.
But, personally, I prefer to just launch classic when needed. Otherwise, I just leave it closed.
I'm not sure if you are familiar with classic mode on OS X or not, but it isn't the same as dual booting, or having 2 separate operating systems installed. You don't choose between them when you boot, you just run classic on top of OS X.
Apple has actually made it so that many of the newer machines can only use classic mode on top of OS X. The newer machines cannot even boot OS 9 as a stand-alone operating system.
I can understand if you don't want to install the classic mode for OS X, but it would probably be more convenient to do that than to purchase a new copy of AppleWorks.
Best of luck to you whatever you decide. Let me know if you have other questions I might be able to answer for you. -
Is there an upgrade path for 2007 macs?
I have a 2007 Mac Pro. Does anyone know of an upgrade path to OSX Mavericks?
There isn't one. That machine is basically stuck with Lion (10.7.5) as the last OS X version it can run. It lacks 64-bit EFI which is a requirement for OS X Mountain Lion and Mavericks.
-
Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff path
$ dmesg -l err
[ 6.330201] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache2
[ 6.332384] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache1
[ 6.334041] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache1
[ 6.730564] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache3
[ 6.732213] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache3
[ 6.997304] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 6.999960] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 7.003235] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.005881] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.194594] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.197369] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.207859] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.210477] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.240459] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 7.243114] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 8.062829] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
[ 8.065328] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
I've been getting this since I upgraded systemd last week. I tried fixing some of these by removing partitions with the same label that I wasn't using, which worked. The reason I have so many partitions with the same label is due to btrfs. Each partition that makes up a volume in btrfs has the same label. Apparently systemd doesn't like this.
Everything on my system seems to be working fine, however I would like to stop these errors since they are annoying/scary, but without having to reduce all my volumes to single.
Last edited by nstgc (2015-04-26 15:53:20)I'm running with a wired-only set up. I'll have to wait for the weekend to look into the wireless angle, however I doubt that is the cause for me.
Following dront78's example below is the output of "# hwinfo --partitions"
75: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bdUI.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda1
Device Files: /dev/sda1, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part1, /dev/disk/by-id/wwn-0x6829766019904589826x-part1, /dev/disk/by-partuuid/77f1354c-3b20-454d-ba60-9dbab9bc8640, /dev/disk/by-uuid/ff387510-d0ad-498f-8d1b-576b26ed103e
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
76: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2pkM.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda2
Device Files: /dev/sda2, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part2, /dev/disk/by-id/wwn-0x6829766019904589826x-part2, /dev/disk/by-partuuid/44596381-4cfe-4a2d-8e7b-f6427cc089d0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
77: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: W__Q.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda3
Device Files: /dev/sda3, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part3, /dev/disk/by-id/wwn-0x6829766019904589826x-part3, /dev/disk/by-partuuid/c9b404ec-f407-4081-a69c-9b10360d4cf7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
78: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: z9FV.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda4
Device Files: /dev/sda4, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part4, /dev/disk/by-id/wwn-0x6829766019904589826x-part4, /dev/disk/by-partuuid/69c0972d-51ed-429c-acea-6e1afd7ebb1f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
80: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: h4pj.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb1
Device Files: /dev/sdb1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part1, /dev/disk/by-id/wwn-0x17950130428369588225x-part1, /dev/disk/by-uuid/2c0f1039-2d4b-4f75-8fa4-529d19cd18fc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
81: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 8G3o.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb2
Device Files: /dev/sdb2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part2, /dev/disk/by-id/wwn-0x17950130428369588225x-part2, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
82: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bRJs.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb3
Device Files: /dev/sdb3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part3, /dev/disk/by-id/wwn-0x17950130428369588225x-part3, /dev/disk/by-label/old-raid1, /dev/disk/by-uuid/dfa989d8-edac-4c7e-b6fc-45237e6a0ebc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
83: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2dZw.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb4
Device Files: /dev/sdb4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part4, /dev/disk/by-id/wwn-0x17950130428369588225x-part4, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
85: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: mX79.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc1
Device Files: /dev/sdc1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part1, /dev/disk/by-id/wwn-0x4611505914592251905x-part1, /dev/disk/by-uuid/80780835-de4b-462c-b7f0-2b389d3e2c2f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
86: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: DjND.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc2
Device Files: /dev/sdc2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part2, /dev/disk/by-id/wwn-0x4611505914592251905x-part2, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
87: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: gudH.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc3
Device Files: /dev/sdc3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part3, /dev/disk/by-id/wwn-0x4611505914592251905x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
88: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 74uL.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc4
Device Files: /dev/sdc4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part4, /dev/disk/by-id/wwn-0x4611505914592251905x-part4, /dev/disk/by-label/old-aroot, /dev/disk/by-uuid/b396dd50-e3f1-4b74-8cac-7d8d79a75386
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
90: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: r_Ra.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd1
Device Files: /dev/sdd1, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part1, /dev/disk/by-id/wwn-0x14865109125905272832x-part1, /dev/disk/by-partlabel/Microsoft\x20reserved\x20partition, /dev/disk/by-partuuid/f3e9ce24-988d-40ef-bd5c-6313c808bef2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
91: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: IAie.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd2
Device Files: /dev/sdd2, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part2, /dev/disk/by-id/wwn-0x14865109125905272832x-part2, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/f3344931-99c3-11e4-8601-806e6f6e6963, /dev/disk/by-uuid/30F403F0F403B75E
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
92: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: lLyi.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd3
Device Files: /dev/sdd3, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part3, /dev/disk/by-id/wwn-0x14865109125905272832x-part3, /dev/disk/by-partlabel/EFI\x20system\x20partition, /dev/disk/by-partuuid/ffbaa0cc-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/0DE5-0CB0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
93: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: CXCn.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd4
Device Files: /dev/sdd4, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part4, /dev/disk/by-id/wwn-0x14865109125905272832x-part4, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/ffbaa0b6-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/FE2648382647EFE7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
94: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: fiSr.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd5
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd5
Device Files: /dev/sdd5, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part5, /dev/disk/by-id/wwn-0x14865109125905272832x-part5, /dev/disk/by-label/flbck, /dev/disk/by-partuuid/bd84f197-066e-4b9e-bf9b-b0b3a4090cde, /dev/disk/by-uuid/832bcc8d-836e-4b4e-8d9c-0a19f5bcf7dd
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
95: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 6uiv.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd6
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd6
Device Files: /dev/sdd6, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part6, /dev/disk/by-id/wwn-0x14865109125905272832x-part6, /dev/disk/by-partuuid/8f77bc79-ba57-462e-8beb-d09db5c77490
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
96: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: oKuO.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd7
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd7
Device Files: /dev/sdd7, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part7, /dev/disk/by-id/wwn-0x14865109125905272832x-part7, /dev/disk/by-partuuid/7ca3eb27-d198-4915-9c71-e96fa7a34d8b, /dev/disk/by-uuid/fd43f1bd-9f52-41b7-badc-4ab7881473ee
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
97: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: GW8T.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd8
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd8
Device Files: /dev/sdd8, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part8, /dev/disk/by-id/wwn-0x14865109125905272832x-part8, /dev/disk/by-partuuid/550f9e19-c0ec-4474-9e98-84c727854158
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
98: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: cPdt.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd10
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd10
Device Files: /dev/sdd10, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part10, /dev/disk/by-id/wwn-0x14865109125905272832x-part10, /dev/disk/by-label/bckup, /dev/disk/by-partuuid/de7eaa1e-66b0-4058-ad71-d0f8ea470b2f, /dev/disk/by-uuid/723d7788-8514-4777-8e07-e0faa48c9a83
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
100: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: wRm+.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde1
Device Files: /dev/sde1, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part1, /dev/disk/by-id/wwn-0x9832618751734861824x-part1, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
101: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: Nd04.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde2
Device Files: /dev/sde2, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part2, /dev/disk/by-id/wwn-0x9832618751734861824x-part2, /dev/disk/by-uuid/aa19d2cf-e59d-4277-a5e6-d0078ede6d3b
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
102: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: qoG8.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde3
Device Files: /dev/sde3, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part3, /dev/disk/by-id/wwn-0x9832618751734861824x-part3, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
103: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: H_WC.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde4
Device Files: /dev/sde4, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part4, /dev/disk/by-id/wwn-0x9832618751734861824x-part4
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
105: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: +u4R.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf1
Device Files: /dev/sdf1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part1, /dev/disk/by-id/wwn-0x8355873293896667137x-part1, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
106: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: S4LV.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf2
Device Files: /dev/sdf2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part2, /dev/disk/by-id/wwn-0x8355873293896667137x-part2, /dev/disk/by-uuid/96fa47c5-061d-4849-8582-7186cc1695d2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
107: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: vFbZ.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf3
Device Files: /dev/sdf3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part3, /dev/disk/by-id/wwn-0x8355873293896667137x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
108: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: NRrd.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf4
Device Files: /dev/sdf4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part4, /dev/disk/by-id/wwn-0x8355873293896667137x-part4, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
i don't have time to look at this in detail this morning, but I will this afternoon.
Thank you for all the replies. Have any of you found this to actually be damaging?
[edit] In an effort to not be completely lazy, and because I was curious, I did check a bit into netctl. Running "$ netctl list" returned exactly nothing. I have no profiles.
[edit2]
I just ran "$ dmesg -l err" on my laptop and I'm not getting any errors.
Last edited by nstgc (2015-04-27 15:09:46) -
Still no Graphics upgrade path?
I bought my Macpro 2.66 almost a year ago with the stock 7300 card planning on upgrading to a better card. I didn't take the 512mb card due to all the overheating issues. Here it is a year later and still no upgrade path. A new card finally comes out and it can't be used on Macs that aren't even a year old! I have been a mac user since the G3 models but I am really considering switching to a PC due to the graphics card situation. I called Apple and they basically said there was no upgrade path but hinted that there was a solution. I was told 'I have heard of people putting other cards in them but you have to make sure that the drivers are available'. When pressed to tell me which cards however the rep said "I don't know'. So I was given the distinct impression that there is an upgrade out there but the apple reps aren't allowed to say. Any help for this dilemma would be appreciated. Thanks
Message was edited by: PianoPeteI'll go with Kappy on this. But my guess is that they want one card that is universal and supports any Mac Pro. Retrofitting and having two cards with different ROM (EFI32 for us, EFI64 for 2008) would be a nightmare to support.
Who knows? maybe the poor Nvidia 8800 performance has them talking to ATI about something... but pure speculation.
I too hoped that PCI Express would open more doors, not be left with 7300GT or a two year old plus X1900.
To tell the truth, one reason I played around with Vista has been to use a Nvidia 8600 GTS but I still need the 7300 (and no conflict with the two).
See http://www.barefeats.com which has about the best information for now. -
WLC code upgrade path questions
We running WCS 6.0.132(lastest) and our controllers are on 4.2.130, we now want to upgrade to keep up with the times, but don't want to change over to capwap yet.
Question1:What's the latest LWAPP release code??
Question2:Whats the differences between 4.2.207 (cisco's support page says this is the latest release) but there's even releases with much higher versions ie 6.0 how does this work it's very confusing to workout an upgrade path
CheersHi Tyrone,
I'm not an expert on Versioning but here are some basic details in response
to your query
4.2.207 is the latest release on the 4.2 Train and is probably an excellent choice
if you are avoiding CAPWAP for the time being. You will see in the link below that
there are multiple "simultaneous" Trains for the WLC (and most Cisco products). People
were not huge fans of the early 5.x Trains (quite buggy) and CAPWAP was introduced
in 5.2 and forward so this is why 4.2.207 seems like a good fit for you
In controller software release 5.2 or later, Cisco lightweight access points use the IETF standard Control and Provisioning of Wireless Access Points protocol (CAPWAP) in order to communicate between the controller and other lightweight access points on the network. Controller software releases prior to 5.2 use the Lightweight Access Point Protocol (LWAPP) for these communications.
CAPWAP, which is based on LWAPP, is a standard, interoperable protocol that enables a controller to manage a collection of wireless access points. CAPWAP is being implemented in controller software release 5.2 for these reasons:
To provide an upgrade path from Cisco products that use LWAPP to next-generation Cisco products that use CAPWAP
To manage RFID readers and similar devices
To enable controllers to interoperate with third-party access points in the future
LWAPP-enabled access points can discover and join a CAPWAP controller, and conversion to a CAPWAP controller is seamless. For example, the controller discovery process and the firmware downloading process when you use CAPWAP are the same as when you use LWAPP. The one exception is for Layer 2 deployments, which are not supported by CAPWAP.
You can deploy CAPWAP controllers and LWAPP controllers on the same network. The CAPWAP-enabled software allows access points to join either a controller that runs CAPWAP or LWAPP. The only exception is the Cisco Aironet 1140 Series Access Point, which supports only CAPWAP and therefore joins only controllers that run CAPWAP. For example, an 1130 series access point can join a controller that runs either CAPWAP or LWAPP whereas an 1140 series access point can join only a controller that runs CAPWAP.
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008064a991.shtml
4.2.207 was released 24/Jul/2009 which does make it the second newest version available in any train.
http://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html
Cheers!
Rob -
Can Muse be used to create a site that requires a CMS with multiple user accounts?
Hi, I am new to Adobe Muse and I would like to understand some specific things about the software. I have been comissioned to create a gallery website which requres a cms for use with mulitple accounts for the users/ artists to display seperate profiles and submit work to. Does Muse have this functionality and if possible to answer, how would I do this? I have looked at the tutorials on Adobe for Muse but I have not seen anything related to this, only the Busines Catlalyst website management software (if indeed it is software). Are there any tutorials on this or could I please be directed to one if no direct answer can be given here as I appreciate it is quite an indepth question. Thanks..
Wait for the new version of Muse which should be published during the first quarter of this year. I guess that in the new Muse version could be basic CMS features?
Best Regards
TaikaJim -
How can I install after a hard drive failure with only upgrade disk?
I've been using Photoshop since 1998 but my HDD recently suffered a complete failure and I've had to change the drive. Unfortunately, I don't have my original Photoshop disk, only a CS2 and CS5 upgrade disk (with both serial numbers). Is there any way round this problem? Many thanks in advance for any replies.
Welcome to the forum.
My upgrade path started with Ps version 2.5. That was the last full version, that I had. All the rest were upgrades from there, though to CS 2.
When I went to install CS 2, I was asked for the CS version. I had both the upgrade disc and the S/N (my S/N's went through a couple of iterations, over the decades). In my case, the CS version disc was inserted, found and the installation went smoothly.
Now, while I have CS 5 (and 5.5 and 6), I never installed CS 5, it was just part of the upgrade path, to get me to CS 6 at the end. With my CS 5 S/N, CS 6 installed fine.
That was what worked for me, and I hope will work for you too. Keep that CS 2 disc handy, as you might need to insert that into the multi-drive, at a point in the CS 5 installation.
The one worry that I would have, with an HDD failure, would be Activation, as you probably did not Deactivate Ps, before that failure. For that, should you be up against your allowed Activations, you will likely want to call Adobe Customer Support, and explain your problem. They should be able to reset the Activations, and help you.
Good luck,
Hunt -
Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path
Hi everybody,
I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
<04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
<04-25-2014 02:06:47> ********************************************
<04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
minimum supported installed build version is [7804].
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Unsupported upgrade path; Error;
Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
<04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Active Replica MP; Passed
<04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Parent site replication status; Passed
<04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
=====
<04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;
SQL Server sysadmin rights; Passed
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int; SQL Server sysadmin rights
for reference site; Passed
<04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Site server computer account administrative rights; Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server security mode; Passed
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
<04-25-2014 02:07:09> INFO: Target computer is a Windows server.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Unsupported site server operating system version for Setup; Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Domain membership; Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Pending system restart; Passed
<04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server version; Passed
<04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Edition; Passed
<04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
Instance:.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Tcp Port; Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
<04-25-2014 02:07:09> INFO: SQL Server memory is limited.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Configuration for SQL Server memory usage; Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
<04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
Server to reserve a minimum of 8 gigabytes (GB) of memory.
<04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int; SQL Server process memory allocation;
Warning; Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
http://go.microsoft.com/fwlink/p/?LinkId=233759.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Case-insensitive collation on SQL Server; Passed
<04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFO: getaddrinfo returned success.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Validate FQDN of SQL Server Computer; Passed
<04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
<04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Primary FQDN; Passed
<04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
=====
<04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
<04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Failover Cluster; Passed
<04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Deployment Tools installed; Passed
<04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int; Windows Preinstallation Environment
installed; Passed
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
SMS Provider machine has same domain as site server; Passed
<04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:10> ***************************************************
<04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
<04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
Prerequisite checking result into the registry
<04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
<04-25-2014 02:07:10> INFO: Setting registry values
If you wonder whether it might be related to this error:
-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
I've already tried the
Preinst /DELSITE XXX command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
Finally, the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
the impression that it's being cached somehow.
Any help would be highly appreciated,
Thank you.
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSEHello again everybody,
I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
primary sites.
If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
DELETE
FROMServerDataWHERESiteCode='XXX'
DELETE
FROMSC_SiteDefinitionWHERESiteCode='XXX'
And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
Thank you all anyways for your answers and comments,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE -
Error Message: "This upgrade path is not supported"
Scenario
During the process of upgrade to Windows 10 Technical Preview, we may encounter the error “This upgrade path is not supported. Please close Setup and re-launch from the root of the media or go back and pick a different installation
choice.” in the Compatibility report.
Analysis
Step 1: Perform the scenario 1: the upgrade installation fails.
Reproduce this error following the steps below:
Download the Windows 10 Technical Preview ISO installation file.
Extract the ISO installation file to C:\New folder, and now the location of the installation file is
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\.
Click setup.exe from the installation file, and then click
Install now.
Setup is starting, and then get two options Upgrade and
Custom which is the classic setup wizard which we can see during booting from DVD.
Click Upgrade to run upgrade installation, however, the error occurs.
It seems that it is impossible to perform upgrade installation to Windows 10 Technical Preview, although it is fine to click
Custom to perform clean installation which cannot keep the personal setting and applications.
However, what we want is upgrade installation, not clean installation.
Step 2: Perform the scenario 2: the upgrade installation works fine.
If extract the ISO installation to C:\New in the above step2, click the
setup.exe from the installation file C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\, the upgrade installation would work fine, which is as shown the following two figures:
Step 3: Check the setupact.log
file which contains information about setup actions during the installation of the two scenarios.
Scenario 1: Check the setupact.log file of the scenario 1. The detailed information is shown as below:
2014-10-14 19:03:40, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:03:42, Info UI Will launch ConX setup experience
2014-10-14 19:03:42, Info UI Launching ConX setup experience
2014-10-14 19:03:42, Info UI Launching C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
2014-10-14 19:03:44, Info UI Unknown command line for ConX setup experience. Launching legacy setup experience.
2014-10-14 19:03:44, Info UI Determining if we are in WDS/Unattend mode
2014-10-14 19:03:44, Info UI No need to hide autorun
2014-10-14 19:03:44, Info [0x0a000a] UI Autorun:Autorun core successfully initialized!!!
2014-10-14 19:03:44, Info [0x0a000b] UI Autorun:Autorun UI successfully initialized!!!
2014-10-14 19:03:44, Info UI AppWindow has layout style 0
2014-10-14 19:03:45, Info UI NavWindow has layout style 0
2014-10-14 19:03:45, Info [0x0a011c] UI WizardDialogPost::SetActive
2014-10-14 19:04:57, Info [0x0a018e] UI Passing command line parameter ("C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\setup.exe /HideWelcome /uilanguage:en-US /targetlanguage:en-US") to IBS.
Scenario 2: Check the setupact.log file of the scenario 2. The detailed information is shown as below:
2014-10-14 19:08:04, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:08:05, Info UI Will launch ConX setup experience
2014-10-14 19:08:05, Info UI Launching ConX setup experience
2014-10-14 19:08:05, Info UI Launching C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
According to the two logs, we can get the following points:
In scenario 1, it would invoke the SetupPrep.exe in the source folder directly to perform an installation preparation. However, it failed to recognize the path
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe. Then it would launch legacy setup.
In the scenario 2, Windows setup would be redirected to the ConX setup to perform upgrade installation automatically.
So, what is the difference of the scenario 1 and 2 to bring the different results of upgrade installation?
Workaround
Based on lots of testing, we find that if there is no space in the extracting location of the ISO installation
file, the upgrade installation would work fine.
What’s more, we can get the meaning of the two setup models in the setupact.log:
Legacy setup: it is same with setup from DVD boot.
ConX setup: it would check the compatibility and language UI for upgrade preparation, then perform migration and upgrade directly.
Additional Resource
From the release of Windows 10 Technical Preview, many users have installed and tested Windows 10 Technical Preview, we still hope more and more users would download and install Windows 10 Technical Preview for test, and provide
us your feedback.
Download Windows Technical Preview
http://windows.microsoft.com/en-us/windows/preview-iso
Download Windows Technical Preview for Enterprise
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-technical-preview-for-enterprise
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.Hello,
I would guess that existence of a space in the folder name is what the issue is. Try removing the space from the folder name and see if works. New_Folder for example
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. -
With each upgrade of Firefox, I have a harder and harder time, getting to the links provided in my emails. Some times I am able to trick the link into working, if I continue to to try every link in the email, but most of the time, I just have to give up. I know that I need to change something, maybe in the settings, but I don't know what.
Please help me. I am considering just going back to Internet Explorer.This did not solve my problem. I can sometimes click on a link (word) provided in an email, that leads to a site, but it does not list the website address!! It works sometimes, providing me with a chance to enable links for this address or enable link (I think basically for just that one time).
-
Issue with SAP GUI 7.30 launching with users upgrading from 7.10
We started rolling out SAP 7.30 GUI Final 7300.3.7.117 out to people, and we've ran into this error with people who had upgraded from SAP GUI 7.10.
Our environmental variable uses saplogon.ini (SAPLOGON_INI_FILE) and points to c:\windows\saplogon.ini
I don't know why the program is trying to search for saplogontree.xml.
I've tried uninstalling, rebooting, reinstalling. Deleting some of the %appdata% SAP folders.
I need some guidance as people who upgraded from GUI 7.20 do not run into this issue.This popup would make sense Jason,as the path C:\Windows\SapLogonTree.xml would not be a valid path to this file.
Really, 7.10 should not have been used at all as an upgrade path as this had finished support in 2009
If you have a small number of users with 7.10, it's recommend to remove it via add/remove programs in the OS, then install a clean 7.30 gui.
The environment variable should not point to C:\Windows\ at all since this is a restricted folder in
Windows Vista and higher, and will only cause further trouble later on in the updates
See note http://service.sap.com/sap/support/notes/1409494
Jude
Maybe you are looking for
-
After I updated user for i phone 4 s iCloud password is no way I can not phone and e-mail address has been blocked. I did not bring the solution to Turkey APPLE chief BILKOM is forgotten the password and e-mail address in the e-mail address asking fo
-
Pls, help. Activation lock with old ID not my ID when update ios 7.0.4
i bought old iphone 4s with ios 7.0.3, i signed in my ID icloud in setting. i update ios to 7.0.4. I get activation lock with old id not my id. I can't pass activation lock my iphone, pls...help me
-
PReq quantity not synchronized with work order.
Hello, I have a work order for which created Preq for external component with quantity 10. Then when converting PReq into PO I have change the quantity to 5. So I have PO with quantity 5 but in the work order requirement quantity is still 10. When tr
-
Hi, I need to develop a report to fetch the components in service order with their quantity (The material numbers available in service order components tab and quantity). I am using table RESB to fetch the same, but it brings even the deleted mateial
-
Oracle 8i (8.1.7.4.1) Windows 2000 Server Using DBNS_UTILITY.COMPILE_SCHEMA('SYS', FALSE) some objects compile and others become invalid. Help please